Consumed API from other projects
...
Steps for Releasing and branching | ||||||
|---|---|---|---|---|---|---|
| 1. Go to latest merged review of repo and comment “stage-release” | ||||||
| 2. It will trigger 2 Jenkins jobs - stage-master & docker-stage-master | ||||||
3. Once the jobs are successful, create a yaml file for releasing maven artifacts first and raise a review. This file can typically be generated using this script:
| ||||||
4. Once that is merged and build is successful, create another container.yaml file for releasing docker image and raise a review. This file can typically be generated using this script:
NOTE: Drools-applications will require a 2nd "stage-release" to be done after step 3 due to the way it is built. The docker image requires the java artifacts to be released first, which are packaged into the image. | ||||||
| 5. Once that is merged and build is successful, go to nexus3.onap.org and verify that the image was released | ||||||
| 6. Bump the snapshot version to next patch version and raise a review - I use this command “mvn versions:set -DnewVersion=2.5.1-SNAPSHOT” | ||||||
| 7. Once that is merged and build is successful, go to gerrit and create a “frankfurt” branch. (ONLY needed when we are branching and proceeding to new release) | ||||||
8. Once the branch is created, bump the master branch to next minor version using the same maven command and raise a review | ||||||
| 9. Finally go to frankfurt branch and change the .gitreview file to point to frankfurt as default branch and raise the review. |