Last modified: 2014-05-21 20:41:33 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67602, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65602 - [Trebuchet] `git deploy` should be automatable
[Trebuchet] `git deploy` should be automatable
Status: NEW
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
wmf-deployment
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-05-21 20:41 UTC by Bryan Davis
Modified: 2014-05-21 20:41 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Bryan Davis 2014-05-21 20:41:15 UTC
I would like to have Jenkins run `git deploy` in beta to deploy some repos in response to zuul triggers. Optimally the process would look something like this:

* cd /src/deployment/repo/repo
* git deploy start
* git fetch origin
* git reset --hard origin/master
* git deploy sync --wait-for-fetch --wait-for-checkout --timeout=360
* git deploy report --detailed sync

The mythical `--wait-for-fetch` and `--wait-for-checkout` command line switches would tell Trebuchet to keep waiting in the fetch and checkout phases until all minions reported back. The `--timeout` option would set a maximum duration (in seconds) for the entire `git deploy sync` process to complete. If this was reached Trebuchet should exit with a non-zero exit code and an appropriate error message.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links