In the event of some unrecoverable Nexus issue leading to loss of the staging repo, I wouldn't see any concern with simply running a deployment from the tag to create a new staging repo. The release is the source archive as far as the foundation is concerned, with the binaries only for convenience, so the release itself wouldnt really be affected in any way by this, and a new deployment should be the same except for any embedded timestamps.
I tend to release the Nexus staging repo first when I am completing things after a vote, before I add the release to the release area of the dist repo. That being the case, I wouldn't have got to the 'actual release' until after the rest was successfull anyway. Though a failure wouldnt necessarily stop me doing that, since it is essentially two seperate things in the end, as the source is the release. Robbie On 22 June 2018 at 16:16, Clebert Suconic <[email protected]> wrote: > On our release procedures, what would happen if Nexus failed to > release the repository? > > We would need to restart the whole process and another vote to > validate checksums, etc.. even if it's the same git TAG? (I could just > recover release.properties created and re-upload it.. but that's a > different binary generation.. signed again). > > I'm asking that because I freaked out for a few minutes where nexus > did not want to release 2.6.2 for my repository. > > A simple retry fixed it. but it made me think.. what is the procedure > if it didn't? > > I could of course ask help for Infra, but What would happen if I had > to drop the repository and redo the release? > > Did anyone ever experienced issues during the release phase?
