canmove, Confirmed users
112
edits
CIDuty/How To/Update Python dependencies: Difference between revisions
CIDuty/How To/Update Python dependencies (view source)
Revision as of 01:29, 26 April 2019
, 26 April 2019Apop moved page CIDuty/How To//Update Python dependencies to CIDuty/How To/Update Python dependencies
m (Apop moved page CIDuty/How To//Update Python dependencies to CIDuty/How To/Update Python dependencies) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 9: | Line 9: | ||
# If you have the Ok, start the update | # If you have the Ok, start the update | ||
# Monitoring the update on puppet mail and papertrail | # Monitoring the update on puppet mail and papertrail | ||
# In case of failure rollback | # In case of failure - rollback | ||
# Weekly admin task | |||
# Questions and Answers | # Questions and Answers | ||
| Line 16: | Line 17: | ||
Go to https://github.com/mozilla-releng/build-puppet and click on Pull requests and look for "Scheduled weekly dependency update for week X" ( where X is the current week ) | Go to https://github.com/mozilla-releng/build-puppet and click on Pull requests and look for "Scheduled weekly dependency update for week X" ( where X is the current week ) | ||
[[File:Repo.png| | [[File:Repo.png|none]] | ||
= Check the dependencies and how they affect the systems = | = Check the dependencies and how they affect the systems = | ||
| Line 23: | Line 24: | ||
For example : ptyprocess 0.6.0 | For example : ptyprocess 0.6.0 | ||
[[File:Dep 1.png| | [[File:Dep 1.png|none]] [[File:Change log.png|none]] | ||
[[File: | Also to check how are the files changed : Go to Files change tab to see what will be changed and how : | ||
[[File:Ewpo change.png]] | |||
= Check if there are any releases on the go also check with the release team = | = Check if there are any releases on the go also check with the release team = | ||
| Line 33: | Line 36: | ||
= Running the update = | = Running the update = | ||
After checking all the dependencies and there | After checking all the dependencies and if there are no releases, you can start the update, by merging the pyup update into master | ||
= Monitoring the update on puppet mail and papertrail = | = Monitoring the update on puppet mail and papertrail = | ||
In order to monitor the updates you should subscribe to puppet mail : [https://groups.google.com/a/mozilla.com/forum/#!forum/releng-puppet-mail Releng Puppet Mail] | |||
You should also check and monitor using papertrail : [https://papertrailapp.com Papertrail] | |||
Ex of search : [https://papertrailapp.com/groups/1141234/events?q=balrog_scriptworker&focus=958572280949137435 Balrog scriptworker] | |||
= In case of failure - Rollback = | |||
In case of any failure it is needed to create a patch that reverts the changes. | |||
For this is needed to be created a ticket. | |||
= In case of update to Signing Servers = | |||
Please note if there's signingserver changes so someone from the short list (https://github.com/mozilla-releng/build-puppet/blob/master/manifests/moco-config.pp#L239) will need to restart those instances within a few hours of this being merged. | |||
= Weekly admin task = | |||
Every Monday, the admin who is on duty needs to check the build puppet, for the dependencies . | |||
If there is a "Scheduled weekly dependency update for week X" then he will need to update them following the action list | |||
| Line 56: | Line 79: | ||
A : The monitoring should be done the Puppet mail and also on papertrail | A : The monitoring should be done the Puppet mail and also on papertrail | ||
Q : | Q : Who are affected when an update or more goes wrong ? | ||
A : Possibly, anyone! | |||