Skip to content

Commit a76a16d

Browse files
authored
update release docs (#501)
1 parent ac01064 commit a76a16d

File tree

1 file changed

+3
-14
lines changed

1 file changed

+3
-14
lines changed

docs/releases.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -96,19 +96,8 @@ Someone with access to the scriptworker package on `pypi.python.org` needs to do
9696

9797
That creates source tarball and wheel, and uploads it.
9898

99-
## Puppet
99+
## Rollout
100100

101-
Connect to Releng VPN.
101+
To roll out to the scriptworker kubernetes pools, wait for a few minutes after the pypi upload, run [pin.sh](https://github.com/mozilla-releng/scriptworker-scripts/blob/master/maintenance/pin.sh) to bump all the workers, get review on that change, then push to the `production` branch when you're ready to roll out. (Use the `production-___script` branches if you only want to update scriptworker on a subset of workers.) We'll see a notification in Slack `#releng-notifications` as each pool rolls out.
102102

103-
Copy the wheel from `dist/` to `releng-puppet2.srv.releng.mdc1.mozilla.com`:
104-
105-
```bash
106-
scp dist/scriptworker-$VERSION-py2.py3-none-any.whl releng-puppet2.srv.releng.mdc1.mozilla.com:
107-
ssh releng-puppet2.srv.releng.mdc1.mozilla.com
108-
cd /data/python/packages-3.x
109-
sudo mv -n ~/scriptworker-$VERSION-py2.py3-none-any.whl .
110-
```
111-
112-
Bump the [scriptworker version](https://hg.mozilla.org/build/puppet/file/b67965cc83e6/modules/signing_scriptworker/manifests/init.pp#l43) in the appropriate scriptworker instance puppet configs.
113-
114-
If desired, test in your [user environment](https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/HowTo/Set_up_a_user_environment) first. Otherwise, get review, land, and merge to production.
103+
To roll out to the mac signers, get review for a patch like [this](https://github.com/mozilla-platform-ops/ronin_puppet/commit/d08be5473a425e12a3d865a038a3b6a9f71c1548) and merge. The mac signer maintainers will roll out to the `production-mac-signing` branch as appropriate. We don't get notifications anywhere, so we likely just need to give this a half hour or so to roll out.

0 commit comments

Comments
 (0)