This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener). # Fixed URLs ## Fixed Success These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended. * [ ] http://openjdk.java.net/projects/code-tools/jmh/ with 1 occurrences migrated to: https://openjdk.java.net/projects/code-tools/jmh/ ([https](https://openjdk.java.net/projects/code-tools/jmh/) result 200). * [ ] http://www.example.com/jira/rest/api/2/issue/10000 with 1 occurrences migrated to: https://www.example.com/jira/rest/api/2/issue/10000 ([https](https://www.example.com/jira/rest/api/2/issue/10000) result 200). * [ ] http://docs.spring.io/spring-data/%s/docs/%s with 1 occurrences migrated to: https://docs.spring.io/spring-data/%s/docs/%s ([https](https://docs.spring.io/spring-data/%s/docs/%s) result 301). # Ignored These URLs were intentionally ignored. * http://127.0.0.1:8080/capture-benchmarks with 1 occurrences * http://localhost:8888 with 2 occurrences Original pull request: #108.
- Infrastructure requirements
- Pivotal VPN account
- User account (for SCP access) on
docs.af.pivotal.io. Needs to be registered within localsettings.xmlfor a server namedstatic-dot-s2. - Credentials for
buildmasteraccounts 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) insettings.xmlfor server with idsonatype.
- Add an
application-local.propertiesto 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.