canmove, Confirmed users
112
edits
CIDuty/How To/High Pending Counts: Difference between revisions
added info for escalation teams and about FIC
m (Apop moved page ReleaseEngineering/How To/Dealing with high pending counts to CIDuty/How To/High Pending Counts) |
(added info for escalation teams and about FIC) |
||
| Line 63: | Line 63: | ||
For an example of this problem, see {{bug|1203104}} | For an example of this problem, see {{bug|1203104}} | ||
You can also check by running '''Firefox Infra Changelog''' script. The tool builds a change log of commits happening on git and hg that could affect Firefox CI Infra. | |||
The script can be found here : https://github.com/mozilla-releng/firefox-infra-changelog | |||
The following command will check for new commits and update the files. | |||
<pre> | |||
python update-files.py | |||
</pre> | |||
Also, the client script can be run using the following arguments, depending the needs : | |||
<pre> | |||
Short Flag Long Flag Description | |||
-c --complete Runs script for all available repositories | |||
-g --git Runs script only for repos that are on GitHub | |||
-hg --mercurial Runs script only for repos that are on Mercurial | |||
-m --manual Let the user choose for which repositories the script will run | |||
-l --logger Activate logger output in the console | |||
-d --days Generate the changelog.md for <int> amount of days. | |||
-u --update Runs script for all available repositories and auto push the changes to github | |||
</pre> | |||
If infra issue has been found, depending the case, this should be escalated to the right team ( network, data center, etc ). | |||
Please check the following document for [https://docs.google.com/spreadsheets/d/1pUFq6Z5M5a1ydbSzxNjQivFfryVoksdXa9xXTg9gtzc/edit#gid=0 escalation teams]. | |||
==== Are we underbidding for AWS spot instances? ==== | ==== Are we underbidding for AWS spot instances? ==== | ||