Polishing.

Having verified the latest variant of Spring Data Release, including smoke tests, there is no need to keep the commented-out sections about the prior smoke tests/conclude steps in Jenkinsfile.
This commit is contained in:
Greg L. Turnquist
2023-04-18 14:46:10 -05:00
parent a366895fe2
commit d4ca98a87b

12
Jenkinsfile vendored
View File

@@ -62,19 +62,7 @@ pipeline {
steps {
script {
sh "ci/build-spring-data-release-cli.bash"
// sh "ci/prepare-and-build.bash ${p['release.version']}"
/*slackSend(
color: (currentBuild.currentResult == 'SUCCESS') ? 'good' : 'danger',
channel: '#spring-data-dev',
message: (currentBuild.currentResult == 'SUCCESS')
? "`${env.BUILD_URL}` - Build and deploy passed! Conduct smoke tests then report back here."
: "`${env.BUILD_URL}` - Push and distribute failed!")
input("SMOKE TEST: Did the smoke tests for ${p['release.version']} pass? Accept to conclude and distribute the release.")
*/
// sh "ci/conclude.bash ${p['release.version']}"
sh "ci/build-and-distribute.bash ${p['release.version']}"
slackSend(