Define process for 1.x releases

[gshif]

• If release branch does not exist, create one
  • TBD
  • influxdb repo:
  • checkout the branch we are releasing from. For example, if we are releasing from 1.8 branch, then run git checkout 1.8 command
  • pull the latest changes to the branch: git pull
  • get all the commits from previous tagged release (or from previous release) until now. For example, the previous tagged release was v1.8.0rc0, running git rev-list -n 1 v1.8.0rc0 will return the commit for the v1.8.0rc0, let's call it commit_1 Running git log -1 will return the latest commit for the branch - commit_2 Get all of the commits by running git log commit_1...commit_2 --oneline command. Check the CHANGELOG to ensure all of the changes are present. If not, then create a branch based on a release branch and update CHANGELOG. If it is a GA release, update the date of the release. After successful build, merge the changes into the 1.8 branch.
  • Once 1.8 branch build completes successfully, make changes in plutonium repo You can monitor the build here: https://ci.influxdb.com/job/influxdb/job/1.8/

[gshif]

• plutonium repo:
  • checkout the branch we are releasing from, e.g. git checkout 1.8
  • pull the latest changes to the branch: git pull
  • update Gopkg.lock file with the latest influxdb sha (if needed) by running dep ensure -update github.com/influxdata/influxdb
  • get all the commits from previous tagged release till now and make sure all of the changes are reflected in the CHANGELOG file
  • Once build with the above changes completes successfully, merge the changes (for example) into 1.8. You can monitor build status by using your's PR link here: https://ci.influxdb.com/job/Plutonium-Unit-Tests/view/change-requests/. Please NOTE: most likely some of the unit tests will fail. One of the reasons could be flaky tests. You can re-run build by doing the following:
    • Click on the build number of the failed build under Build History
    • On the build page, click on Replay button. You can comment the stage if you want to skip it by using when { expression { return false }}, for example if you want to skip stage Query regression test, you would type when { expression { return false }} right after stage('Query regression test') {
    • Click on Run button
    • If unit tests keep failing because of the flaky tests, skip this step as well (see above).
  • When 1.8 branch build completes successfully (can check its status here https://ci.influxdb.com/job/Plutonium-Unit-Tests/job/1.8/) tag a commit by following following step(s):
    • from (in our example) github.com/influxdata/plutonium: 1.8, run command: git tag -a v1.8.0rc2 -m v1.8.0rc2 && git push origin v1.8.0rc2 updating the version and rc number to the correct one
  • Go to https://ci.influxdb.com/job/PlutoniumBuildTaggedRelease/ page and:
    • Click on configure and under Pipeline -> Branches to build make changes to Branch Specifier field updating it with correct tag and save the changes
    • From the https://ci.influxdb.com/job/PlutoniumBuildTaggedRelease/ page click on Build Now link. You might face the same problem as in regular builds - flaky unit tests - so use the steps to skip them.
    • Once tagged build completes, the results will be posted in #releases channel

[kevinhogan111]

https://influxdb.atlassian.net/wiki/spaces/QA/pages/1074167862/Building+InfluxDB+1.x+for+Releases