ReleaseEngineering/How To/allthethings.json: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
m (added script to generate allthethings.json) |
(add debug information) |
||
| Line 10: | Line 10: | ||
Here's how you deploy a new change: | Here's how you deploy a new change: | ||
* catlee has a checkout on cruncher | * catlee has a checkout on cruncher | ||
= Debug in production = | |||
These are the steps to follow: | |||
* Connect to the VPN with 'push' as your password (you will get a DUO prompt; accept it) | |||
ssh `whoami`g@cruncher.build.mozilla.org | |||
sudo su - catlee | |||
> From crontab: | |||
> */15 * * * * $HOME/allthethings/make_allthethings.sh | mail -E -s '[allthethings] all the things' catlee@mozilla.com | |||
Revision as of 15:27, 16 October 2015
Some tools are starting to feed on allthethings.json.
Here's how you can generate it locally:
hg clone https://hg.mozilla.org/build/braindump cd braindump/community ./generate_allthethings_json.sh
Here's how you deploy a new change:
- catlee has a checkout on cruncher
Debug in production
These are the steps to follow:
- Connect to the VPN with 'push' as your password (you will get a DUO prompt; accept it)
ssh `whoami`g@cruncher.build.mozilla.org sudo su - catlee > From crontab: > */15 * * * * $HOME/allthethings/make_allthethings.sh | mail -E -s '[allthethings] all the things' catlee@mozilla.com