spring-data-dev-tools

Files

Oliver Drotbohm 594ca16875 #113 - Deployment promotion is now skipped for public artifacts.

As we publish public artifacts (i.e. GA and service releases) directly to Maven Central, there's no need for the promotion step and it currently produces error output (fortunately not breaking the build). With this commit in place, this is now changed to simply skip that step and print informative output.

2019-04-02 12:38:47 +02:00

src

#113 - Deployment promotion is now skipped for public artifacts.

2019-04-02 12:38:47 +02:00

application-local.template

#5 - Create release tickets and release versions for Jira-tracked projects.

2016-04-05 18:43:37 +02:00

lombok.config

A way too big commit.

2016-02-10 12:01:06 +01:00

pom.xml

#107 - URL Cleanup.

2019-03-20 10:23:26 -05:00

readme.md

#75 - Document additional release steps.

2018-05-17 11:26:08 +02:00

Spring Data Release Tools.sonargraph

#18 - Added (currently empty) Sonargraph architecture description.

2016-04-05 18:47:53 +02:00

readme.md

Infrastructure requirements

Pivotal VPN account
User account (for SCP access) on docs.af.pivotal.io. Needs to be registered within local settings.xml for a server named static-dot-s2.
Credentials for buildmaster accounts on https://repo.spring.io.
Credentials for https://oss.sonatype.org (to deploy and promote GA and service releases, need deployment permissions for org.springframework.data) in settings.xml for server with id sonatype.

Add an application-local.properties to the project root and add the following properties:

git.username - Your GitHub username.
git.password - Your GitHub password or API key.
git.author - Your full name (used for preparing commits).
git.email - Your email (used for preparing commits).
maven.mavenHome - Pointing to the location of your Maven installation.
deployment.api-key - The API key to use for artifact promotion.
deployment.password - The password of the deployment user (buildmaster).

Run mvn package appassembler:assemble && sh target/appassembler/bin/spring-data-release-shell
Pre-release checks

Make sure that:

Upgrade dependencies in Spring Data Build parent pom (mind minor/major version rules)
All release tickets are present ($ tracker releasetickets $trainIteration)
Review open tickets for release
Self-assign release tickets ($ tracker prepare $trainIteration)
Announce release preparations to mailing list

Commands to execute

$ release prepare $trainIteration
$ release build $trainIteration
$ release conclude $trainIteration
$ git push $trainIteration
$ git push $trainIteration --tags
$ release distribute $trainIteration
$ git backport changelog $trainIteration --target $targets
$ foreach $target -> git push $target

Post-release tasks

Close Jira tickets and GitHub release tickets.
Create release tickets for the next train iteration, archive old release versions. Close Jira versions/GitHub milestones.

$ tracker close $trainIteration
$ tracker create releaseversions $trainIteration.next
$ tracker create releasetickets $trainIteration.next
$ tracker archive $trainIteration.previous

Update versions in Sagan with $ sagan update $releasetrains.
Announce release (Blog, Twitter) and notify downstream dependency projects as needed. Dev-tools can assist you with $ announcement $trainIteration. Make sure to remove the changelog link to Envers as this module has no changelog.