canmove, Confirmed users
112
edits
CIDuty/How To/Update Python dependencies: Difference between revisions
Jump to navigation
Jump to search
m
CIDuty/How To/Update Python dependencies (view source)
Revision as of 22:47, 24 July 2018
, 24 July 2018→Questions and Answers
m (→Introduction) |
|||
| Line 40: | Line 40: | ||
= Questions and Answers = | = Questions and Answers = | ||
What do we need to do before update ? | Q : What do we need to do before update ? | ||
We need to check all the dependencies that will be updated, to figure out what could be affected in case of any surprises. | A : We need to check all the dependencies that will be updated, to figure out what could be affected in case of any surprises. | ||
How do we do the update ? | Q : How do we do the update ? | ||
We need to merge pyup-bot patch to the master. | A : We need to merge pyup-bot patch to the master. | ||
When it is recommended to run the update ? | Q: When it is recommended to run the update ? | ||
This should be done, when there are no releases and also it should be wise to ask the release duty team before starting any action. | A : This should be done, when there are no releases and also it should be wise to ask the release duty team before starting any action. | ||
Where and what do we need to monitor when we triggered the update ? | Q : Where and what do we need to monitor when we triggered the update ? | ||
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 | ||
How do we rollback in case of problems/errors ? | Q : How do we rollback in case of problems/errors ? | ||