ci: Automate the process to create a GitHub Release page#1132
Merged
Conversation
7 tasks
Member
Author
|
@spotbugs/everyone this PR is ready to merge, please have a review. |
16d7737 to
74ddb64
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
henrik242
reviewed
Jun 8, 2020
| echo "ossrhPassword=${SONATYPE_PASSWORD}" >> gradle.properties | ||
| echo "keystorepass=${KEYSTORE_PASS}" >> gradle.properties | ||
| ./gradlew publish --no-daemon | ||
| ./gradlew assemble publish --no-daemon --parallel |
Contributor
There was a problem hiding this comment.
Doesn't publish imply assemble? No biggie :)
Member
Author
There was a problem hiding this comment.
Yes, Eclipse plugin and site aren't targeted to publish, so we need to invoke assemble explicitly.
This was referenced Jun 8, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently the GitHub Release is created manually, so we sometimes have mis-operation like #755.
To avoid it, it's nice to automate the process to create a GitHub Release page for each release.
It is also good to list checksum of each artifact in the page, then user can verify integrity of our products.
TBD: Travis CI also creates GitHub Release, so to avoid conflict, need to move the build for Eclipse Plugin from Travis to GitHub Actions. refs #1123done.Sample output of the
createReleaseBodytaskYou can preview this markdown at this Gist.