Spring/spring-batch
Spring/spring-batch
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-batch.git synced 2024-07-14 23:56:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated Release process for v5 (markdown)

Mahmoud Ben Hassine 2023-03-01 22:05:52 +01:00
parent 8e92f277a5
commit e1ab16fd29
1 changed files with 32 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
Release-process-for-v5.md

@ -34,6 +34,22 @@
Check uploaded jars in http://repo.spring.io/libs-milestone-local/org/springframework/batch and do a smoke test with the deployed milestone version: check the integrity of the artifacts to see if jars are not corrupted or empty, etc.
#### Test within an IDE
* Download the [release test project](https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip) and unzip it
* Open it in your IDE and update the release version to test + comment the spring-staging repository
* Run the `MyBatchJobConfiguration` class and then the `MyBatchJobTests` suite
#### Test on the CLI
```
$>wget https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip
$>unzip spring-batch-release-test.zip && cd spring-batch-release-test
$>vim pom.xml # update the release version to test and comment the spring-staging repository
$>mvn exec:java -Dexec.mainClass=MyBatchJobConfiguration # make sure the job is executed correctly
$>mvn test # make sure the tests pass (no functional tests here, we are only checking the integrity of `spring-batch-test.jar`)
```
❗ Heads-up: The "Artifactory Milestone Release" workflow is designed to be idempotent (it has no git side effects). If something is wrong with the milestone release, the same workflow can be re-run with the same version and a new milestone will override the corrupted one on the milestone repository. ❗
## Part 2.2: Release GAs to Maven Central
@ -47,6 +63,22 @@ Check uploaded jars in http://repo.spring.io/libs-milestone-local/org/springfram
Check uploaded jars in http://repo.spring.io/libs-staging-local/org/springframework/batch and do a smoke test with the staged release: check the integrity of the artifacts to see if jars are not corrupted or empty, etc.
##### Test within an IDE
* Download the [release test project](https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip) and unzip it
* Open it in your IDE and update the release version to test + comment the spring-milestones repository
* Run the `MyBatchJobConfiguration` class and then the `MyBatchJobTests` suite
#### Test on the CLI
```
$>wget https://raw.githubusercontent.com/wiki/spring-projects/spring-batch/projects/spring-batch-release-test.zip
$>unzip spring-batch-release-test.zip && cd spring-batch-release-test
$>vim pom.xml # update the release version to test and comment the spring-milestones repository
$>mvn exec:java -Dexec.mainClass=MyBatchJobConfiguration # make sure the job is executed correctly
$>mvn test # make sure the tests pass (no functional tests here, we are only checking the integrity of `spring-batch-test.jar`)
```
❗ Heads-up: The "Artifactory Staging" workflow is designed to be idempotent (it has no git side effects). If something is wrong with staged artifacts, the workflow "Artifactory Staging" can be re-run with the same version and a new release will override the corrupted one on the staging repository. ❗
### Part 2.2.3: Promote the release to Maven Central