GitLab Runner 11.10 release checklist

Previous release checklist issue: #4039 (closed)

GitLab Runner Release manager: @tmaczukin

Release blog post MR: gitlab-com/www-gitlab-com!21184 (merged)

Runner entries need to be added to blog post until: 2019-04-11

First working day after 7th - v11.10.0-rc1 release

check if Pipeline for master is passing:
- add all required fixes to make master Pipeline passing
git checkout master && git pull in your local working copy!
prepare CHANGELOG entries
```
./scripts/prepare-changelog-entries.rb
```
Copy the lines to the beginning of CHANGELOG.md file and add a proper header:
```
v11.10.0-rc1 (TODAY_DATE_HERE)
```

add v11.10.0-rc1 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v11.10.0-rc1" -S

tag and push v11.10.0-rc1:

git tag -s v11.10.0-rc1 -m "Version v11.10.0-rc1" && \
git push origin v11.10.0-rc1

create and push 11-10-stable branch:

git checkout -b 11-10-stable && \
git push -u origin 11-10-stable

checkout to master, update VERSION file to 11.11.0 and push master:

git checkout master; echo -n "11.11.0" > VERSION && \
git add VERSION && \
git commit -m "Bump version to 11.11.0" -S && \
git push

wait for Pipeline for v11.10.0-rc1 to pass
- add all required fixes to make v11.10.0-rc1 passing

update runner helm chart to use v11.10.0-rc1 version

check if Pipeline for master is passing:
- add all required fixes to make master Pipeline passing
go to your local working copy of https://gitlab.com/charts/gitlab-runner
git checkout master && git pull in your local working copy!

set Helm Chart to use v11.10.0-rc1 version of Runner

create new branch, update Runner version and push the branch:

git checkout -b update-runner-to-11-10-0-rc1 && \
sed -i".bak" "s/^appVersion: .*/appVersion: 11.10.0-rc1/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump used Runner version to 11.10.0-rc1" -S && \
git push -u origin update-runner-to-11-10-0-rc1

create Merge Request pointing 0-4-0-stable: https://gitlab.com/charts/gitlab-runner/merge_requests/107

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__rhc_urv_rc1 \
    --milestone 11.10 \
    --runner-version 11.10.0-rc1 \
    charts/gitlab-runner \
    update-runner-to-11-10-0-rc1 \
    master \
    runner-version-bump-in-runner-helm-chart \
    "Bump used Runner version to 11.10.0-rc1"

manage to merge the MR

check if Pipeline for master is passing:
- add all required fixes to make master Pipeline passing
git checkout master && git pull in your local working copy!
prepare CHANGELOG entries
```
./scripts/prepare-changelog-entries.rb
```
Copy the lines to the beginning of CHANGELOG.md file and add a proper header:
```
## v0.4.0-rc1 (TODAY_DATE_HERE)
```

add v0.4.0-rc1 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v0.4.0-rc1" -S

bump version of the Helm Chart to 0.4.0-rc1

sed -i".bak" "s/^version: .*/version: 0.4.0-rc1/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump version to 0.4.0-rc1" -S

tag and push v0.4.0-rc1:

git tag -s v0.4.0-rc1 -m "Version v0.4.0-rc1" && \
git push origin v0.4.0-rc1

create and push 0-4-0-stable branch:

git checkout -b 0-4-0-stable && \
git push -u origin 0-4-0-stable

checkout to master, bump version of the Helm Chart to 0.5.0-beta and push master:

git checkout master && \
sed -i".bak" "s/^version: .*/version: 0.5.0-beta/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump version to 0.5.0-beta" -S && \
git push

[-] deploy v11.10.0-rc1

Detailed description of Runners deployment for GitLab.com CI fleet can be found in the runbook.

[-] at RC1 release day: to prmX runners

go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-prm-runners-to-11-10-0-rc1

update version

$EDITOR roles/gitlab-runner-prm.json

In the role definition prepare the override_attributes entry. It should be placed at the top of the file:

"override_attributes": {
  "cookbook-gitlab-runner": {
    "gitlab-runner": {
        "repository": "unstable",
        "version": "11.10.0-rc1"
    }
  }
},

git add roles/gitlab-runner-prm.json && git commit -m "Update prmX runners to v11.10.0-rc1"
git push -u origin update-prm-runners-to-11-10-0-rc1
after pushing the branch, create and manage to merge the chef-repo MR
check the apply to staging job if it tries to update only the changed role
start the manual apply to prod job

[-] after the job is finished execute:

knife ssh -C 1 -afqdn 'roles:gitlab-runner-prm' -- sudo /root/runner_upgrade.sh &
time wait

[-] next day (if no problems): to rest of the runners

[-] go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-base' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-base' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-runners-to-11-10-0-rc1

[-] remove overrides from prmX runners
```
$EDITOR roles/gitlab-runner-prm.json
```

[-] update version

$EDITOR roles/gitlab-runner-base.json

In the role definition prepare the gitlab-runner entry:

"cookbook-gitlab-runner": {
  "gitlab-runner": {
    "repository": "unstable",
    "version": "{{.Major}}.{{.Minor}}.0-rc{{.RC}}"
  }
}

[-] git add roles/gitlab-runner-prm.json roles/gitlab-runner-base.json && git commit -m "Update runners to v11.10.0-rc1"
[-] git push -u origin update-runners-to-11-10-0-rc1
[-] after pushing the branch, create and manage to merge the chef-repo MR
[-] check the apply to staging job if it tries to update only the changed role
[-] start the manual apply to prod job

[-] after the job is finished execute:

knife ssh -C1 -afqdn 'roles:gitlab-runner-builder' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-gsrm' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-prm' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-srm' -- sudo /root/runner_upgrade.sh &
time wait

New features window is closed - things not merged into master up to this day, will be released with next release.

7 working days before 22th (2019-04-11)

prepare GitLab Runner entries for the release blog post. Items can be generated with ./scripts/changelog2releasepost | less (executed in Runner's local working copy directory)

add release entry:

Add description to the SECONDARY FEATURES list using following template:

- name: GitLab Runner 11.10
  available_in: [core, starter, premium, ultimate]
  documentation_link: 'https://docs.gitlab.com/runner'
  documentation_text: "Read through the documentation of GitLab Runner"
  description: |
    We're also releasing GitLab Runner 11.10 today! GitLab Runner is the open source project
    that is used to run your CI/CD jobs and send the results back to GitLab.

    ##### Most interesting changes:

    * [Add option to specify clone path](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1267)
    * [Improve support for 'git clean'](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1281)
    * [Allow to disable debug tracing](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1286)
    * [Use delayed variable expansion for error check in Windows Cmd](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1260)
    * [Fix color output on Windows](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1208)

    List of all changes can be found in GitLab Runner's [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-runner/blob/v11.10.0/CHANGELOG.md).

Pick into stable branch for RC2 phase

At this moment, until the next RC creation, we're in the pick into stable phase. The release manager should periodically review the list of merged MRs with a pick into X.Y label:

GitLab Runner MRs:

pick: Fix git lfs not getting submodule objects: !1298 (merged)

GitLab Runner's Helm Chart MRs:

For each such Merge Request the release manager should (reveal for details)

Find the merge commit for the Merge Request
Copy the commit reference
Checkout to the branch:
- 11-10-stable for GitLab Runner, or
- 0-4-0-stable for GitLab Runner's Helm Chart

Pick the merge commit with:

git cherry-pick -m 1 [merge commit SHA here]

Remove the Pick into X.Y label from the Merge Request and leave a note that it was picked:

for GitLab Runner use this message:

/unlabel ~"Pick into 11.10"

The MR was picked into `11-10-stable` branch and will be released with RC2

for GitLab Runner's Helm Chart use this message:

/unlabel ~"Pick into 0.4"

The MR was picked into `0-4-0-stable` branch and will be released with RC2

To prepare the _Pick into ..._ MRs list execute:

rrhelper \
    list-pick-mrs-for-rc \
    --non-interactive \
    --do-not-create \
    --major 11 \
    --minor 10  \
    --helm-chart-major 0 \
    --helm-chart-minor 4 \
    4126 2

v11.10.0-rc2 release

check if Pipeline for 11-10-stable is passing:
- add all required fixes to make 11-10-stable Pipeline passing
git checkout 11-10-stable && git pull in your local working copy!
prepare CHANGELOG entries
```
./scripts/prepare-changelog-entries.rb
```
Copy the lines to the beginning of CHANGELOG.md file and add a proper header:
```
v11.10.0-rc2 (TODAY_DATE_HERE)
```

add v11.10.0-rc2 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v11.10.0-rc2" -S

tag and push v11.10.0-rc2:

git tag -s v11.10.0-rc2 -m "Version v11.10.0-rc2" && \
git push origin v11.10.0-rc2

push 11-10-stable branch:

git push origin v11.10.0-rc2 11-10-stable

wait for Pipeline for v11.10.0-rc2 to pass
- add all required fixes to make v11.10.0-rc2 passing

update runner helm chart to use v11.10.0-rc2 version

check if Pipeline for 0-4-0-stable is passing:
- add all required fixes to make 0-4-0-stable Pipeline passing
go to your local working copy of https://gitlab.com/charts/gitlab-runner
git checkout 0-4-0-stable && git pull in your local working copy!

set Helm Chart to use v11.10.0-rc2 version of Runner

create new branch, update Runner version and push the branch:

git checkout -b update-runner-to-11-10-0-rc2 && \
sed -i".bak" "s/^appVersion: .*/appVersion: 11.10.0-rc2/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump used Runner version to 11.10.0-rc2" -S && \
git push -u origin update-runner-to-11-10-0-rc2

create Merge Request pointing 0-4-0-stable: https://gitlab.com/charts/gitlab-runner/merge_requests/108

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__rhc_urv_rc2 \
    --milestone 11.10 \
    --runner-version 11.10.0-rc2 \
    charts/gitlab-runner \
    update-runner-to-11-10-0-rc2 \
    0-4-0-stable \
    runner-version-bump-in-runner-helm-chart \
    "Bump used Runner version to 11.10.0-rc2"

manage to merge the MR

check if Pipeline for 0-4-0-stable is passing:
- add all required fixes to make 0-4-0-stable Pipeline passing
git checkout 0-4-0-stable && git pull in your local working copy!
prepare CHANGELOG entries
```
./scripts/prepare-changelog-entries.rb
```
Copy the lines to the beginning of CHANGELOG.md file and add a proper header:
```
## v0.4.0-rc2 (TODAY_DATE_HERE)
```

add v0.4.0-rc2 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v0.4.0-rc2" -S

bump version of the Helm Chart to 0.4.0-rc2

sed -i".bak" "s/^version: .*/version: 0.4.0-rc2/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump version to 0.4.0-rc2" -S

tag and push v0.4.0-rc2:

git tag -s v0.4.0-rc2 -m "Version v0.4.0-rc2" && \
git push origin v0.4.0-rc2

push 0-4-0-stable:
```
git push origin 0-4-0-stable
```

deploy v11.10.0-rc2

Detailed description of Runners deployment for GitLab.com CI fleet can be found in the runbook.

at RC2 release day: to prmX runners

go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-prm-runners-to-11-10-0-rc2

update version

$EDITOR roles/gitlab-runner-prm.json

In the role definition prepare the override_attributes entry. It should be placed at the top of the file:

"override_attributes": {
  "cookbook-gitlab-runner": {
    "gitlab-runner": {
        "repository": "unstable",
        "version": "11.10.0-rc2"
    }
  }
},

git add roles/gitlab-runner-prm.json && git commit -m "Update prmX runners to v11.10.0-rc2"
git push -u origin update-prm-runners-to-11-10-0-rc2
after pushing the branch, create and manage to merge the chef-repo MR
check the apply to staging job if it tries to update only the changed role
start the manual apply to prod job

after the job is finished execute:

knife ssh -C 1 -afqdn 'roles:gitlab-runner-prm' -- sudo /root/runner_upgrade.sh &
time wait

next day (if no problems): to rest of the runners

go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-gsrm OR roles:gitlab-runner-srm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-gsrm OR roles:gitlab-runner-srm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-runners-to-11-10-0-rc2

update version

$EDITOR roles/gitlab-runner-base.json

In the role definition prepare the gitlab-runner entry:

"cookbook-gitlab-runner": {
  "gitlab-runner": {
    "repository": "unstable",
    "version": "11.10.0-rc2"
  }
}

remove overrides from prmX runners
```
$EDITOR roles/gitlab-runner-prm.json
```
git add roles/gitlab-runner-prm.json roles/gitlab-runner-base.json && git commit -m "Update runners to v11.10.0-rc2"
git push -u origin update-runners-to-11-10-0-rc2
after pushing the branch, create and manage to merge the chef-repo MR
check the apply to staging job if it tries to update only the changed role
start the manual apply to prod job

after the job is finished execute (we're not touching prmX - they are already updated):

knife ssh -C1 -afqdn 'roles:gitlab-runner-builder' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-gsrm' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-srm' -- sudo /root/runner_upgrade.sh &
time wait

Pick into stable branch for RC3 phase

At this moment, until the next RC creation, we're in the pick into stable phase. The release manager should periodically review the list of merged MRs with a pick into X.Y label:

GitLab Runner MRs:

GitLab Runner's Helm Chart MRs:

For each such Merge Request the release manager should (reveal for details)

Find the merge commit for the Merge Request
Copy the commit reference
Checkout to the branch:
- git checkout 11-10-stable && git pull for GitLab Runner, or
- git checkout 0-4-0-stable && git pull for GitLab Runner's Helm Chart

Pick the merge commit with:

git cherry-pick -m 1 [merge commit SHA here]

Remove the Pick into X.Y label from the Merge Request and leave a note that it was picked:

for GitLab Runner use this message:

/unlabel ~"Pick into 11.10"

The MR was picked into `11-10-stable` branch and will be released with `v11.10.0-rc3`

for GitLab Runner's Helm Chart use this message:

/unlabel ~"Pick into 0.4"

The MR was picked into `0-4-0-stable` branch and will be released with `v0.4.0-rc3`

To prepare the `Pick into ...` MRs list execute:

rrhelper \
    list-pick-mrs-for-rc \
    --non-interactive \
    --do-not-create \
    --major 11 \
    --minor 10  \
    --helm-chart-major 0 \
    --helm-chart-minor 4 \
    4126 3

RC3 (if needed)

If any commit was picked into the stable branch since RC2 was released, RC3 version must be released no later than at 18th day of the month or immediately if changes were picked after 18th.

If you need to create RC3 version, then please execute this and follow the created checklist for RC3:

rrhelper \
    create-next-rc-checklist \
    --non-interactive \
    --do-not-create \
    --major 11 \
    --minor 10  \
    --helm-chart-major 0 \
    --helm-chart-minor 4 \
    4126 3

At 19th - the release day of GitLab Runner

check if Pipeline for 11-10-stable is passing:
- add all required fixes to make 11-10-stable Pipeline passing
git checkout 11-10-stable && git pull in your local working copy!
merge all RCx CHANGELOG entries into release entry

Put a proper header at the begining:
```
v11.10.0 (TODAY_DATE_HERE)
```

add v11.10.0 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v11.10.0" -S

tag and push v11.10.0 and 11-10-stable:

git tag -s v11.10.0 -m "Version v11.10.0" && \
git push origin v11.10.0 11-10-stable

checkout to master and merge 11-10-stable into master (only this one time, to update CHANGELOG.md and make the tag available for ./scripts/prepare-changelog-entries.rb in next stable release), push master:
```
git checkout master && \
git pull && \
git merge --no-ff 11-10-stable
# check that the only changes are in CHANGELOG.md
git push
```

update runner helm chart to use v11.10.0 version

check if Pipeline for 0-4-0-stable is passing:
- add all required fixes to make 0-4-0-stable Pipeline passing
go to your local working copy of https://gitlab.com/charts/gitlab-runner
git checkout 0-4-0-stable && git pull in your local working copy!

set Helm Chart to use v11.10.0 version of Runner

create new branch, update Runner version and push the branch:

git checkout -b update-runner-to-11-10-0 && \
sed -i".bak" "s/^appVersion: .*/appVersion: 11.10.0/" Chart.yaml && \
rm Chart.yaml.bak && git add Chart.yaml && \
git commit -m "Bump used Runner version to 11.10.0" -S && \
git push -u origin update-runner-to-11-10-0

create Merge Request pointing 0-4-0-stable: https://gitlab.com/charts/gitlab-runner/merge_requests/110

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__rhc_urv_stable \
    --milestone 11.10 \
    --runner-version 11.10.0 \
    charts/gitlab-runner \
    update-runner-to-11-10-0 \
    0-4-0-stable \
    runner-version-bump-in-runner-helm-chart \
    "Bump used Runner version to 11.10.0"

manage to merge the MR

check if Pipeline for 0-4-0-stable is passing:
- add all required fixes to make 0-4-0-stable Pipeline passing
git checkout 0-4-0-stable && git pull in your local working copy!
merge all RCx CHANGELOG entries into release entry

Put a proper header at the begining:
```
## v0.4.0 (TODAY_DATE_HERE)
```

add v0.4.0 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v0.4.0" -S

bump version of the Helm Chart to 0.4.0

sed -i".bak" "s/^version: .*/version: 0.4.0/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump version to 0.4.0" -S

tag and push v0.4.0 and 0-4-0-stable:

git tag -s v0.4.0 -m "Version v0.4.0" && \
git push origin v0.4.0 0-4-0-stable

checkout to master and merge 0-4-0-stable into master (only this one time, to update CHANGELOG.md and make the tag available for ./scripts/prepare-changelog-entries.rb in next stable release), push master:
```
git checkout master && \
git pull && \
git merge --no-ff 0-4-0-stable
# check that the only changes are in CHANGELOG.md
git push
```

update Runner's chart version used by GitLab: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27508

create branch

rrhelper \
    --dry-run \
    create-branch \
    gitlab-org/gitlab-ce \
    update-gitlab-runner-helm-chart-to-0-4-0

create Merge Request

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__gce_rhcvu \
    --milestone 11.11 \
    --runner-version 11.10.0 \
    --helm-chart-version 0.4.0 \
    gitlab-org/gitlab-ce \
    update-gitlab-runner-helm-chart-to-0-4-0 \
    master \
    runner-helm-chart-upgrade-in-gitlab-ce \
    "Update GitLab Runner Helm Chart to 0.4.0/11.10.0"

Adjust and apply the patch to the GitLab CE sources

See the patch draft

Adjust the following patch (set proper current version; set the Merge Request ID in the CHANGELOG entry file) and save it at /tmp/patch.gitlab-ce.

cat > /tmp/patch.gitlab-ce << EOF
diff --git a/app/models/clusters/applications/runner.rb b/app/models/clusters/applications/runner.rb
index 0c0247da1fb..f17da0bb7b1 100644
--- a/app/models/clusters/applications/runner.rb
+++ b/app/models/clusters/applications/runner.rb
@@ -3,7 +3,7 @@
 module Clusters
   module Applications
     class Runner < ActiveRecord::Base
-      VERSION = '0.3.0'.freeze
+      VERSION = '0.4.0'.freeze

       self.table_name = 'clusters_applications_runners'

diff --git a/changelogs/unreleased/update-gitlab-runner-helm-chart-to-0-4-0.yml b/changelogs/unreleased/update-gitlab-runner-helm-chart-to-0-4-0.yml
new file mode 100644
index 00000000000..7d92929221f
--- /dev/null
+++ b/changelogs/unreleased/update-gitlab-runner-helm-chart-to-0-4-0.yml
@@ -0,0 +1,5 @@
+---
+title: Update GitLab Runner Helm Chart to 0.4.0
+merge_request: XXX
+author:
+type: other
diff --git a/spec/models/clusters/applications/runner_spec.rb b/spec/models/clusters/applications/runner_spec.rb
index 3d0735c6d0b..8ad41e997c2 100644
--- a/spec/models/clusters/applications/runner_spec.rb
+++ b/spec/models/clusters/applications/runner_spec.rb
@@ -46,7 +46,7 @@ describe Clusters::Applications::Runner do
     it 'should be initialized with 4 arguments' do
       expect(subject.name).to eq('runner')
       expect(subject.chart).to eq('runner/gitlab-runner')
-      expect(subject.version).to eq('0.3.0')
+      expect(subject.version).to eq('0.4.0')
       expect(subject).to be_rbac
       expect(subject.repository).to eq('https://charts.gitlab.io')
       expect(subject.files).to eq(gitlab_runner.files)
@@ -64,7 +64,7 @@ describe Clusters::Applications::Runner do
       let(:gitlab_runner) { create(:clusters_applications_runner, :errored, runner: ci_runner, version: '0.1.13') }

       it 'should be initialized with the locked version' do
-        expect(subject.version).to eq('0.3.0')
+        expect(subject.version).to eq('0.4.0')
       end
     end
   end
EOF

Go to your local GitLab CE working directory:

git pull && \
    git checkout update-gitlab-runner-helm-chart-to-0-4-0 && \
    git apply /tmp/patch.gitlab-ce && \
    git add . && \
    git commit -m "Update GitLab Runner Helm Chart to 0.4.0" && \
    git push

update Runner's chart version used by GitLab chart: https://gitlab.com/charts/gitlab/merge_requests/765

create branch

rrhelper \
    --dry-run \
    create-branch \
    charts/gitlab \
    update-gitlab-runner-helm-chart-to-0-4-0

create Merge Request

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__ghc_rhcvu \
    --milestone 11.10 \
    --runner-version 11.10.0 \
    --helm-chart-version 0.4.0 \
    charts/gitlab \
    update-gitlab-runner-helm-chart-to-0-4-0 \
    master \
    runner-helm-chart-upgrade-in-gitlab-helm-chart \
    "Update GitLab Runner Helm Chart to 0.4.0/11.10.0"

Adjust and apply the patch to the GitLab Helm Chart sources

See the patch draft

Adjust the following patch (set proper current version; set the Merge Request ID in the CHANGELOG entry file) and save it at /tmp/patch.gitlab-helm-chart.

cat > /tmp/patch.gitlab-helm-chart << EOF
diff --git a/changelogs/unreleased/update-gitlab-runner-to-0-4-0.yml b/changelogs/unreleased/update-gitlab-runner-to-0-4-0.yml
new file mode 100644
index 00000000..5fd73668
--- /dev/null
+++ b/changelogs/unreleased/update-gitlab-runner-to-0-4-0.yml
@@ -0,0 +1,5 @@
+---
+title: Update gitlab-runner to 0.4.0/11.10.0
+merge_request: XXX
+author:
+type: other
diff --git a/requirements.yaml b/requirements.yaml
index 82a0192a..c6293a8d 100644
--- a/requirements.yaml
+++ b/requirements.yaml
@@ -13,6 +13,6 @@ dependencies:
   repository: https://kubernetes-charts.storage.googleapis.com/
   condition: postgresql.install
 - name: gitlab-runner
-  version: 0.3.0
+  version: 0.4.0
   repository: https://charts.gitlab.io/
   condition: gitlab-runner.install
EOF

Go to your local GitLab Helm Chart working directory:

git pull && \
    git checkout update-gitlab-runner-helm-chart-to-0-4-0 && \
    git apply /tmp/patch.gitlab-helm-chart && \
    git add . && \
    git commit -m "Update GitLab Runner Helm Chart to 0.4.0" && \
    git push

At 22nd - the official day of GitLab release

Not going to deploy v11.10.0 to production: #4126 (comment 162823054)

[-] wait for Pipeline for v11.10.0 to pass
- [-] add all required fixes to make v11.10.0 passing

[-] deploy v11.10.0

Detailed description of Runners deployment for GitLab.com CI fleet can be found in the runbook.

[-] at release day: to prmX runners

[-] go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-prm-runners-to-11-10-0

[-] update version

$EDITOR roles/gitlab-runner-prm.json

In the role definition prepare the override_attributes entry. It should be placed at the top of the file:

"override_attributes": {
  "cookbook-gitlab-runner": {
    "gitlab-runner": {
        "repository": "gitlab-runner",
        "version": "11.10.0"
    }
  }
},

[-] git add roles/gitlab-runner-prm.json && git commit -m "Update prmX runners to v11.10.0"
[-] git push -u origin update-prm-runners-to-11-10-0
[-] after pushing the branch, create and manage to merge the chef-repo MR
[-] check the apply to staging job if it tries to update only the changed role
[-] start the manual apply to prod job

[-] after the job is finished execute:

knife ssh -C 1 -afqdn 'roles:gitlab-runner-prm' -- sudo /root/runner_upgrade.sh &
time wait

[-] next day (if no problems): to rest of the runners

[-] go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-gsrm OR roles:gitlab-runner-srm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-gsrm OR roles:gitlab-runner-srm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-runners-to-11-10-0

[-] update version

$EDITOR roles/gitlab-runner-base.json

In the role definition prepare the gitlab-runner entry:

"cookbook-gitlab-runner": {
  "gitlab-runner": {
    "repository": "gitlab-runner",
    "version": "11.10.0"
  }
}

[-] remove overrides from prmX runners
```
$EDITOR roles/gitlab-runner-prm.json
```
[-] git add roles/gitlab-runner-prm.json roles/gitlab-runner-base.json && git commit -m "Update runners to v11.10.0"
[-] git push -u origin update-runners-to-11-10-0
[-] after pushing the branch, create and manage to merge the chef-repo MR
[-] check the apply to staging job if it tries to update only the changed role
[-] start the manual apply to prod job

[-] after the job is finished execute (we're not touching prmX - they are already updated):

knife ssh -C1 -afqdn 'roles:gitlab-runner-builder' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-gsrm' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-srm' -- sudo /root/runner_upgrade.sh &
time wait

At 24th - 11.10.1 patch release

check if Pipeline for 11-10-stable is passing:
- add all required fixes to make 11-10-stable Pipeline passing
git checkout 11-10-stable && git pull in your local working copy!
Cherry pick
prepare CHANGELOG entries
```
./scripts/prepare-changelog-entries.rb
```
Copy the lines to the beginning of CHANGELOG.md file and add a proper header:
```
v11.10.1 (TODAY_DATE_HERE)
```

add v11.10.1 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v11.10.1" -S

tag and push v11.10.1:

git tag -s v11.10.1 -m "Version v11.10.1" && \
git push origin v11.10.1

push 11-10-stable branch:
```
git push origin v11.10.1 11-10-stable
```
wait for Pipeline for v11.10.1 to pass
- add all required fixes to make v11.10.1 passing

update runner helm chart to use v11.10.1 version

check if Pipeline for 0-4-0-stable is passing:
- add all required fixes to make 0-4-0-stable Pipeline passing
go to your local working copy of https://gitlab.com/charts/gitlab-runner
git checkout 0-4-0-stable && git pull in your local working copy!

set Helm Chart to use v11.10.1 version of Runner

create new branch, update Runner version and push the branch:

git checkout -b update-runner-to-11-10-1 && \
sed -i".bak" "s/^appVersion: .*/appVersion: 11.10.1/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump used Runner version to 11.10.1" -S && \
git push -u origin update-runner-to-11-10-1

create Merge Request pointing 0-4-0-stable: https://gitlab.com/charts/gitlab-runner/merge_requests/113

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__rhc_urv_1 \
    --milestone 11.10 \
    --runner-version 11.10.1 \
    charts/gitlab-runner \
    update-runner-to-11-10-1 \
    0-4-0-stable \
    runner-version-bump-in-runner-helm-chart \
    "Bump used Runner version to 11.10.1"

manage to merge the MR

check if Pipeline for 0-4-0-stable is passing:
- add all required fixes to make 0-4-0-stable Pipeline passing
git checkout 0-4-0-stable && git pull in your local working copy!
prepare CHANGELOG entries
```
./scripts/prepare-changelog-entries.rb
```
Copy the lines to the beginning of CHANGELOG.md file and add a proper header:
```
## v0.4.1 (TODAY_DATE_HERE)
```

add v0.4.1 CHANGELOG entries and commit

git add CHANGELOG.md && \
git commit -m "Update CHANGELOG for v0.4.1" -S

bump version of the Helm Chart to 0.4.1

sed -i".bak" "s/^version: .*/version: 0.4.1/" Chart.yaml && \
rm Chart.yaml.bak && \
git add Chart.yaml && \
git commit -m "Bump version to 0.4.1" -S

tag and push v0.4.1:

git tag -s v0.4.1 -m "Version v0.4.1" && \
git push origin v0.4.1

push 0-4-0-stable:
```
git push origin 0-4-0-stable
```

update Runner's chart version used by GitLab: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27627

create branch

rrhelper \
    --dry-run \
    create-branch \
    gitlab-org/gitlab-ce \
    update-gitlab-runner-helm-chart-to-0-4-1

create Merge Request

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__gce_rhcvu1 \
    --milestone 11.11 \
    --runner-version 11.10.1 \
    --helm-chart-version 0.4.1 \
    gitlab-org/gitlab-ce \
    update-gitlab-runner-helm-chart-to-0-4-1 \
    master \
    runner-helm-chart-upgrade-in-gitlab-ce \
    "Update GitLab Runner Helm Chart to 0.4.1/11.10.1"

Adjust and apply the patch to the GitLab CE sources

See the patch draft

Adjust the following patch (set proper current version; set the Merge Request ID in the CHANGELOG entry file) and save it at /tmp/patch.gitlab-ce.

cat > /tmp/patch.gitlab-ce << EOF
diff --git a/app/models/clusters/applications/runner.rb b/app/models/clusters/applications/runner.rb
index 0c0247da1fb..f17da0bb7b1 100644
--- a/app/models/clusters/applications/runner.rb
+++ b/app/models/clusters/applications/runner.rb
@@ -3,7 +3,7 @@
 module Clusters
   module Applications
     class Runner < ActiveRecord::Base
-      VERSION = '0.4.0'.freeze
+      VERSION = '0.4.1'.freeze

       self.table_name = 'clusters_applications_runners'

diff --git a/changelogs/unreleased/update-gitlab-runner-helm-chart-to-0-4-1.yml b/changelogs/unreleased/update-gitlab-runner-helm-chart-to-0-4-1.yml
new file mode 100644
index 00000000000..7d92929221f
--- /dev/null
+++ b/changelogs/unreleased/update-gitlab-runner-helm-chart-to-0-4-1.yml
@@ -0,0 +1,5 @@
+---
+title: Update GitLab Runner Helm Chart to 0.4.1
+merge_request: XXX
+author:
+type: other
diff --git a/spec/models/clusters/applications/runner_spec.rb b/spec/models/clusters/applications/runner_spec.rb
index 3d0735c6d0b..8ad41e997c2 100644
--- a/spec/models/clusters/applications/runner_spec.rb
+++ b/spec/models/clusters/applications/runner_spec.rb
@@ -46,7 +46,7 @@ describe Clusters::Applications::Runner do
     it 'should be initialized with 4 arguments' do
       expect(subject.name).to eq('runner')
       expect(subject.chart).to eq('runner/gitlab-runner')
-      expect(subject.version).to eq('0.4.0')
+      expect(subject.version).to eq('0.4.1')
       expect(subject).to be_rbac
       expect(subject.repository).to eq('https://charts.gitlab.io')
       expect(subject.files).to eq(gitlab_runner.files)
@@ -64,7 +64,7 @@ describe Clusters::Applications::Runner do
       let(:gitlab_runner) { create(:clusters_applications_runner, :errored, runner: ci_runner, version: '0.1.13') }

       it 'should be initialized with the locked version' do
-        expect(subject.version).to eq('0.4.0')
+        expect(subject.version).to eq('0.4.1')
       end
     end
   end
EOF

Go to your local GitLab CE working directory:

git pull && \
    git checkout update-gitlab-runner-helm-chart-to-0-4-1 && \
    git apply /tmp/patch.gitlab-ce && \
    git add . && \
    git commit -m "Update GitLab Runner Helm Chart to 0.4.1" && \
    git push

update Runner's chart version used by GitLab chart: https://gitlab.com/charts/gitlab/merge_requests/768

create branch

rrhelper \
    --dry-run \
    create-branch \
    charts/gitlab \
    update-gitlab-runner-helm-chart-to-0-4-1

create Merge Request

rrhelper \
    --dry-run \
    create-merge-request \
    --release-checklist-issue 4126 \
    --replace-link-in-release-checklist-issue link_to_MR__ghc_1 \
    --milestone 11.10 \
    --runner-version 11.10.1 \
    --helm-chart-version 0.4.1 \
    charts/gitlab \
    update-gitlab-runner-helm-chart-to-0-4-0 \
    master \
    runner-helm-chart-upgrade-in-gitlab-helm-chart \
    "Update GitLab Runner Helm Chart to 0.4.1/11.10.1"

Adjust and apply the patch to the GitLab Helm Chart sources

See the patch draft

Adjust the following patch (set proper current version; set the Merge Request ID in the CHANGELOG entry file) and save it at /tmp/patch.gitlab-helm-chart.

cat > /tmp/patch.gitlab-helm-chart << EOF
diff --git a/changelogs/unreleased/update-gitlab-runner-to-0-4-1.yml b/changelogs/unreleased/update-gitlab-runner-to-0-4-1.yml
new file mode 100644
index 00000000..5fd73668
--- /dev/null
+++ b/changelogs/unreleased/update-gitlab-runner-to-0-4-1.yml
@@ -0,0 +1,5 @@
+---
+title: Update gitlab-runner to 0.4.1/11.10.1
+merge_request: XXX
+author:
+type: other
diff --git a/requirements.yaml b/requirements.yaml
index 82a0192a..c6293a8d 100644
--- a/requirements.yaml
+++ b/requirements.yaml
@@ -13,6 +13,6 @@ dependencies:
   repository: https://kubernetes-charts.storage.googleapis.com/
   condition: postgresql.install
 - name: gitlab-runner
-  version: 0.4.0
+  version: 0.4.1
   repository: https://charts.gitlab.io/
   condition: gitlab-runner.install
EOF

Go to your local GitLab Helm Chart working directory:

git pull && \
    git checkout update-gitlab-runner-helm-chart-to-0-4-1 && \
    git apply /tmp/patch.gitlab-helm-chart && \
    git add . && \
    git commit -m "Update GitLab Runner Helm Chart to 0.4.1" && \
    git push

deploy 11.10.1

Detailed description of Runners deployment for GitLab.com CI fleet can be found in the runbook.

at release day: to prmX runners

go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-prm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-prm-runners-to-11-10-1

update version

$EDITOR roles/gitlab-runner-prm.json

In the role definition prepare the override_attributes entry. It should be placed at the top of the file:

"override_attributes": {
  "cookbook-gitlab-runner": {
    "gitlab-runner": {
        "repository": "gitlab-runner",
        "version": "11.10.1"
    }
  }
},

git add roles/gitlab-runner-prm.json && git commit -m "Update prmX runners to v11.10.1"
git push -u origin update-prm-runners-to-11-10-1
after pushing the branch, create and manage to merge the chef-repo MR
check the apply to staging job if it tries to update only the changed role
start the manual apply to prod job

after the job is finished execute:

knife ssh -C 1 -afqdn 'roles:gitlab-runner-prm' -- sudo /root/runner_upgrade.sh &
time wait

next day (if no problems): to rest of the runners

go to your local chef-repo working directory and execute:

knife ssh -afqdn 'roles:gitlab-runner-gsrm OR roles:gitlab-runner-srm' -- sudo systemctl stop chef-client
knife ssh -afqdn 'roles:gitlab-runner-gsrm OR roles:gitlab-runner-srm' -- sudo systemctl is-active chef-client
git checkout master && git pull
git checkout -b update-runners-to-11-10-1

update version

$EDITOR roles/gitlab-runner-base.json

In the role definition prepare the gitlab-runner entry:

"cookbook-gitlab-runner": {
  "gitlab-runner": {
    "repository": "gitlab-runner",
    "version": "11.10.1"
  }
}

remove overrides from prmX runners
```
$EDITOR roles/gitlab-runner-prm.json
```
git add roles/gitlab-runner-prm.json roles/gitlab-runner-base.json && git commit -m "Update runners to v11.10.0"
git push -u origin update-runners-to-11-10-0
after pushing the branch, create and manage to merge the chef-repo MR
check the apply to staging job if it tries to update only the changed role
start the manual apply to prod job

after the job is finished execute (we're not touching prmX - they are already updated):

knife ssh -C1 -afqdn 'roles:gitlab-runner-builder' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-gsrm' -- sudo /root/runner_upgrade.sh &
knife ssh -C1 -afqdn 'roles:gitlab-runner-srm' -- sudo /root/runner_upgrade.sh &
time wait

Before next 7th

chose a release manager
create a Pick into 0.5 label in Helm Chart's project
@release manager: create the new Release Checklist issue: [link to the ISSUE]
```
rrhelper \
    --dry-run \
    create-release-checklist \
    --non-interactive \
    --previous-release-checklist-issue 4126
```
Ensure, that the above command handles:
- adding link to the release blog post's MR
- setting deadline for add entries to release blog post
  
  Please check what deadline is set for General Contributions section in the release blog post Merge Request. It should be 6th working day before the 22nd. In that case we can set our deadline for 7th working day before 22nd, however if the deadline from the MR is earlier, then use the earliest one.

Edited May 02, 2019 by Steve Xuereb