- This line was added.
- This line was removed.
- Formatting was changed.
- Post "recheck" to re-run a verify job. This may be necessary due to intermittent network failures at Jenkins, because a dependency has become available, etc.
- Post "remerge" to re-run a merge job. This may be necessary due to intermittent network failures at Jenkins, to recreate a version of an artifact, etc.
- Post "stage-release" to run a staging job.
- Post "run-sonar" to run the Sonar analysis job (if applicable).
- Post "
Staging Binary Artifacts
In the LF environment, "to stage" means to create an artifact in an ephemeral staging area, a Nexus registry or repository where artifacts are deleted after two weeks. This practice originated with Java-Maven jobs that follow the convention of using a version suffix string "-SNAPSHOT". The Java-Maven merge jobs create jar files and push them to a "snapshot" repository. To stage a Java-Maven artifact, a process that also strips the "-SNAPSHOT" suffix, post a comment "stage-release" on the a Gerrit change set and the build will start on the appropriate branch.
Non-Java-Maven merge jobs such as Docker merge jobs do not use the "-SNAPSHOT" version convention. These merge jobs generally create and push artifacts directly to a staging area. So for non-Java-Maven artifacts there is no staging workflow.
Releasing Binary Artifacts