ReleaseEngineering/How To/allthethings.json: Difference between revisions
< ReleaseEngineering | How To
Jump to navigation
Jump to search
(updated notes) |
m (typo) |
||
| Line 11: | Line 11: | ||
= How to deploy a new change = | = How to deploy a new change = | ||
* Connect to the VPN with 'push' as your password (you will get a DUO prompt; accept it) | * Connect to the VPN with 'push' as your password (you will get a DUO prompt; accept it) | ||
ssh `whoami` | ssh `whoami`@cruncher.build.mozilla.org | ||
sudo su - buildduty | sudo su - buildduty | ||
cd braindump | cd braindump | ||
Revision as of 20:30, 18 December 2015
Some tools are starting to feed on allthethings.json.
Generate locally
Here's how you can generate it locally:
hg clone https://hg.mozilla.org/build/braindump cd braindump/community ./generate_allthethings_json.sh
How to deploy a new change
- Connect to the VPN with 'push' as your password (you will get a DUO prompt; accept it)
ssh `whoami`@cruncher.build.mozilla.org sudo su - buildduty cd braindump hg pull -u
How the file is generated
Run from a crontab:
*/15 * * * * $HOME/braindump/community/generate_allthethings_json.sh
Then the file is synced from cruncher to secure.pub.m.o once an hour.