Open zabetak opened 1 year ago
At the moment, I am trying to see if there is a graceful way to recover and continue with the publishDist task. Simply adding the missing nexus.txt
in the appropriate place and re-running ./gradlew publishDist
will not work cause it will fail trying to move/cp the svn artifacts.
Finally, I decided to manually perform the remaining steps (hopefully I didn't miss anything):
orgapachecalcite-1200
git checkout main
git merge calcite-1.34.0-rc0
git push origin main
git tag -a calcite-1.34.0 7dfd641baeb0e1b26dec04da5241c3999fe0ac6a -m "Tag explicitly 1.34.0 release without -rc suffix"
git push origin calcite-1.34.0
The best way to handle this would be using Nexus server itself for associating "release candidates" with "staging repositories".
I did try contributing the feature to gradle-nexus/publish-plugin
, unfortunately, the authors were not responsive: https://github.com/gradle-nexus/publish-plugin/pull/145
According to the comments there some part of the change was merged in https://github.com/gradle-nexus/publish-plugin/pull/201 Do you think that we could build on top of that or we are missing more things?
They went with a separate FindStagingRepository
task rather than teaching the existing InitializeStagingRepository
task to lookup the repository.
Apparently, if initializeStagingRepository
was able to do both "find if exists" and "create if missing", then it would be way easier to use.
It might be something like https://github.com/vlsi/vlsi-release-plugins/pull/41 + findStagingRepository
would do the trick, however, I'm not willing to spend more time time on reverse-engineering GNPP code.
nexus.txt
is not a pressing issue for me at the moment, and I'm balancing between:
Trying to publish the RC0 for calcite the
:releaseRepository
task failed.While I was waiting for the vote duration to pass, I was working on other stuff switching/building/cleaning branches along the way. Unsurprisingly the
build/stagingRepositories/nexus.txt
was deleted leading to the error below.