octopus:releasepipeline
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
octopus:releasepipeline [2015/06/03 22:48] Fatih Degirmenci added genesis sha1 |
octopus:releasepipeline [2016/02/24 18:44] (current) Aric Gardner |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== OPNFV Process to prepare the release ====== | ====== OPNFV Process to prepare the release ====== | ||
| - | This page describes the steps to prepare the Arno release. | + | This page describes the steps to prepare the Brahmaputra release. |
| - | For later releases there will be a different process. | + | |
| - | ===== Steps to take for Release ===== | + | ====== Brahmaputra Release ====== |
| - | - Based on input from BGS and FuncTest, TSC decides on | + | PTLs of Brahmaputra participating projects are responsible of |
| - | * The exact version of ISO, deploy and test scripts and documents to use in the release | + | |
| - | * The release tag name | + | |
| - | - Based on the decision of TSC, Octopus identifies/extracts the SHA1s for the repos genesis and functest from Jenkins build/deploy/test jobs. | + | |
| - | - Octopus identifies SHA1s for the repos pharos, octopus, opnfvdocs, and releng and confirms them with respective PTLs. | + | |
| - | - Octopus provides git instructions to PTLs in order to apply tags. | + | |
| - | - PTLs tag corresponding/identified revisions/SHA1s in all the repos that are part of the release with agreed tag. (genesis, functest, pharos, octopus, opnfvdocs, releng) | + | |
| - | - PTLs create maintenance branch in all the repos for the projects that are participating in Arno. \\ (Instructions will be provided by Octopus). | + | |
| - | - Octopus team run final deploy and verify on the release revision. | + | |
| - | - Once validated LF copies the final artifacts and documents to Arno release storage (see below): | + | |
| - | - LF creates links to released artifacts and documents on download pages: www.opnfv.org/software/download | + | |
| - | - Marketing team send release announcement mail. | + | |
| - | ===== Release Tag ===== | + | * Identifying the SHA1 to apply the tag on and release |
| + | * Tagging the SHA1 with the release tag, **brahmaputra.1.0** | ||
| + | * If valid, tagging the Docker images with the release tag, **brahmaputra.1.0** | ||
| + | * Identifying the exact versions of the artifacts (ISO, RPM, documents, etc. if valid) with the help from documentation, infra, and LF. | ||
| + | * Making sure the correct artifacts are linked/referred on release page. | ||
| - | arno.2015.1.0 | + | ===== Steps to take for Brahmaputra Release ===== |
| - | ===== Maintenance Branch ===== | + | * PTLs tag corresponding/identified revisions/SHA1s on **stable/brahmaputra** branch in respective repos |
| + | * LF is notified regarding the final release artifacts | ||
| + | * LF copies the final release artifacts and documents to Brahmaputra release storage | ||
| + | * LF creates links to released artifacts and documents on download pages: www.opnfv.org/software/<tbd> | ||
| + | * Marketing team send release announcement mail | ||
| - | stable/arno | + | ===== Brahmaputra Release Tag ===== |
| - | ===== Storage Locations for Final Artifacts ===== | + | **brahmaputra.1.0** |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/fuel/arno.2015.1.0.fuel.iso | + | ===== Storage Locations for Final Brahmaputra Artifacts ===== |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/fuel/arno.2015.1.0.fuel.iso.md5sum | + | TBD |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/fuel/release-notes.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/fuel/install-guide.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/foreman/arno.2015.1.0.foreman.iso | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/foreman/arno.2015.1.0.foreman.iso.md5sum | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/foreman/release-notes.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/foreman/install-guide.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/docs/user-guide.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/docs/functest.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/docs/pharos-spec.arno.2015.1.0.pdf | + | |
| - | * http://artifacts.opnfv.org/arno.2015.1.0/docs/opnfv-jenkins-slave-connection.arno.2015.1.0.pdf | + | |
| - | ====== git instructions ====== | + | ====== Brahmaputra git tagging instructions ====== |
| - | Committers will apply the tags to the genesis, octopus, releng*, pharos, functest and opnfvdocs repos and create branches for maintenance. | + | PTLs of Brahmaputra participating projects will apply the tags in respective repos. |
| - | ===== SHA1s to Apply Tags and Create Branches on ===== | + | ===== SHA1s to Apply Tags on for SR1 ===== |
| + | |||
| + | SHA1s of the repos are identified by PTLs. If the project is integrated to other projects (such as installer projects) it is important to communicate with these projects as well. | ||
| + | |||
| + | To select the SHA1 to apply the tag for, you can use Gerrit web interface or the git commands as listed below. | ||
| + | |||
| + | * Using Gerrit Web Interface: | ||
| + | * https://gerrit.opnfv.org/gerrit/gitweb?p=<**YOUR PROJECT NAME**>.git;a=shortlog;h=refs/heads/stable/brahmaputra | ||
| + | * Click one of the commits listed on the page. The SHA1 is the one listed in commit field. | ||
| + | * Using Git command | ||
| + | * git checkout stable/brahmaputra | ||
| + | * git log --graph | ||
| - | ^ Repo ^ SHA1 ^ Tag/Branch Status ^ | ||
| - | | genesis | 321aff9 | | | ||
| - | | functest | 3af6557 | Done | | ||
| - | | pharos | cdf8591 | Done | | ||
| - | | opnfvdocs| 9d00c5d | Done | | ||
| - | | octopus | 4da0ef5 | Done | | ||
| - | | releng | 305051a | Done | | ||
| Line 60: | Line 50: | ||
| * git fetch origin | * git fetch origin | ||
| + | * git checkout stable/brahmaputra | ||
| * git checkout <**SHA1**> | * git checkout <**SHA1**> | ||
| - | * git tag -am "arno.2015.1.0" arno.2015.1.0 | + | * git tag -am "brahmaputra.1.0" brahmaputra.1.0 |
| - | * git push origin arno.2015.1.0 | + | * git push origin brahmaputra.1.0 |
| - | Please get the SHA1 for your project from the table above. | + | If you get the error |
| + | ! [remote rejected] brahmaputra.1.0 -> brahmaputra.1.0 (prohibited by Gerrit) | ||
| + | This is because you are not the author of the commit being tagged. email helpdesk and I will add forge rights to refs/tags/* on your repo. | ||
| - | Please contact aricg and/or other Octopus members on #opnfv-octopus channel if you experience any issues. | ||
| - | ===== Branching ===== | ||
| - | |||
| - | * Click the link for your project from below list | ||
| - | * genesis: https://gerrit.opnfv.org/gerrit/#/admin/projects/genesis,branches | ||
| - | * functest: https://gerrit.opnfv.org/gerrit/#/admin/projects/functest,branches | ||
| - | * pharos: https://gerrit.opnfv.org/gerrit/#/admin/projects/pharos,branches | ||
| - | * octopus: https://gerrit.opnfv.org/gerrit/#/admin/projects/octopus,branches | ||
| - | * opnfvdocs: https://gerrit.opnfv.org/gerrit/#/admin/projects/opnfvdocs,branches | ||
| - | * Fill in the boxes as shown below | ||
| - | * Branch Name: stable/arno | ||
| - | * Initial Revision: <**SHA1**> | ||
| - | * Click "Create Branch" | ||
| - | |||
| - | Please get the SHA1 for your project from the table above. | ||
| Please contact aricg and/or other Octopus members on #opnfv-octopus channel if you experience any issues. | Please contact aricg and/or other Octopus members on #opnfv-octopus channel if you experience any issues. | ||
| - | |||
| - | Please note that releng won't be branched off. | ||
| - | |||
octopus/releasepipeline.1433371735.txt.gz · Last modified: 2015/06/03 22:48 by Fatih Degirmenci
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
