Projects that release on their own would like a way promote their own releases without having to open a helpdesk ticket. There are a couple ways we can look into this:

1) Allow committers to login to Nexus with their own accounts and click the promote button

This method would allow them to use the Nexus web interface and self promote using their own accounts. The other benefit here I think is that they would be able to use lftools to publish their own signatures rather than asking for helpdesk to do it since this requires the ability to create staging repos as well.

2) Create a jenkins job that can deploy

This method is similar to the Gerrit option 2 from RELENG-424 where a predefined job can promote the build. A problem here though is if we allow Gerrit comment trigger then anyone with an account can release any arbitrary staging repo. Unless we can figure out how to limit it to only the project committers this method is not a good option.

Potential idea that's not fleshed out yet...

Create a lf-releng branch in a project. In the branch a project will supply a release.txt containing details on which staging repo is being released as well as a m2repo containing signatures for artifacts in the release. On merge a promotion job is triggered that will push the signatures to a new staging repo and release the 2 staging repos.

If the promote job fails for some reason the project will need to submit another patch (doesn't have to change any files as long as the data is still valid it will work) and the verify and merge job cycle happens again.