This page explains how a project can release independently.
A project can produce a staging repository by using one of the following methods against the {project-name}-maven-stage-{stream} job:
stage-release
against any patch for the stream to buildBuild with Parameters
in Jenkins Web UI for the jobThis job performs the following duties:
The files taglist.log and project.bundle can be used later at release time to reproduce a byte exact commit of what was built by the Jenkins job. This can be used to tag the release at release time.
Once testing against the staging repo has been completed and project has determined that the staged repo is ready for release. A release can the be performed as follows:
Steps 3-6 as bash: You will need a working GPG config to sign the release Git tag (“-s” option)
PATCH_DIR=/tmp/patches PROJECT=odlparent VERSION=1.2.3 git checkout $(awk '{print $NF}' "$PATCH_DIR/taglist.log") git fetch "$PATCH_DIR/$PROJECT.bundle" git merge --ff-only FETCH_HEAD git tag -asm "$PROJECT $VERSION" "v$VERSION" git push origin "v$VERSION"
Once complete the Git tag should be available in Gerrit and the Artifacts should appear in the Nexus opendaylight.release repo.
You may also want to use visual panels to communicate related information, tips or things users need to be aware of. |
Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.
|