Skip to content

Latest commit

 

History

History
28 lines (20 loc) · 1.52 KB

RELEASING.adoc

File metadata and controls

28 lines (20 loc) · 1.52 KB

Spring Cloud GCP release process

The actual release process is triggered by the release admin and happens together with the rest of the Spring Cloud release. In order to simplify that process, here is a list of prerequisites to be performed before asking the release admin to run the release scripts.

  1. Manually change the value of TRACKING_HEADER_PROJECT_VERSION in UsageTrackingHeaderProvider to the version being released from the interim BUILD-SNAPSHOT value.

  2. Ensure that modules that shouldn’t be released have the maven-deploy-plugin configuration set to <skip>true</skip>. For GA releases this should be configured under the central Maven profile.

    <build>
	<plugins>
		<plugin>
			<artifactId>maven-deploy-plugin</artifactId>
			<configuration>
				<skip>true</skip>
			</configuration>
		</plugin>
	</plugins>
</build>

  3. Wait for the release scripts to have been run by the release admin.

  4. Make sure that the release tag was automatically added by the release process.

  5. Change the TRACKING_HEADER_PROJECT_VERSION in UsageTrackingHeaderProvider back to BUILD-SNAPSHOT.

  6. Make sure that the Spring Boot Initializr is updated to support the new version of Spring Cloud GCP.