...
Once your self release file was merged and processed by "gerrit-release-verify" and "gerrit-release-merge"...
- Do not DO NOT attempt to revert files in releases/ → Even if the release was not needed, we need to keep track on what happened in that repo also the tag needs to be kept in the repo
- Do not DO NOT attempt to re-tag the repo with the same version → this will fail as the gerrit-release-merge job already tagged it
- Do not DO NOT modify releases files → Once a releases file is merged, it is immediately processed. If the team needs to release a new build number, please bump your versions and generate another stage-release
- Do not DO NOT re-use the same stage-release build number for multiple releases files → Once an autorelease package is pushed, it is closed and it cannot be re-released.
- MAKE SURE your project is 100% free from using nexus-staging-maven-plugin. This was a must do in the global-jjb migration and teams still using it WILL BE facing issues deploying all their artifacts.
- Using this plugin, pre-deploys image in a bad way before lftools has a chance to compile all artifacts needed for the release candidate