CIDuty/How To: Difference between revisions
< CIDuty
Jump to navigation
Jump to search
(→Alerts) |
|||
| Line 60: | Line 60: | ||
===== See Also ===== | ===== See Also ===== | ||
: Relevant [https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Training_-_Relevant_Buildduty_Bugs | : Relevant [https://wiki.mozilla.org/ReleaseEngineering/Buildduty/Training_-_Relevant_Buildduty_Bugs ciduty bugs] that would be suitable for training | ||
Revision as of 04:03, 21 December 2018
Alerts
- Command queues
- High Pending Counts
- Processes
- Pending Scriptworker Tasks
- Puppet Freshness
- Build4h not updating
- Machine Tracking
- Perform a Reconfig
- Work with Golden AMIs
Puppet
- Build DEBs
- Build DMGs
- Build RPMs
- Hack on PuppetAgain
- Push Changes to Production
- Rotate Passwords across Releng Infra
- Setup a User Environment
- Update Mercurial
TaskCluster
- Loan an OSX Worker
- Test a Patch
- Connect to Taskcluster CLI
- Quarantine instances
- Quarantine multiple instances using python code
- Restart/Ping from taskcluster
- Set up or Update a Taskcluster Project
- Restore Azure Table/Blob from Backup
- Modify Gecko Branch Configuration (including twig resets)
- Query Historical Task Analytics
- Provision taskcluster-worker on Packet
- Investigate Audit Logs
- Set up a new Heroku service
- Have a Postmortem/Retrospective
- Connect and Troubleshoot workers in CI
Tree Management
Troubleshooting
Other Tasks
- Upload a Python Package to the Internal Pypi
- Upload a Package/Binary to ToolTool
- Add new secrets to Puppet Hiera
- Work with PyUp Dependency Update PRs
See Also
- Relevant ciduty bugs that would be suitable for training