Python scripts to generate Bugzilla deployment tickets for Mozilla Services.
Note: still under development. FOR OPS USE ONLY.
- Supported projects
- loop-client
- loop-server
- msisdn-gateway
- shavar
- readinglist
- pushgo (no CHANGELOG)
Example
------------------- RELEASE NOTES ------------------- https://github.com/mozilla/loop-client/releases COMPARISONS https://github.com/mozilla/loop-client/compare/0.13.4...0.13.5 https://github.com/mozilla/loop-client/compare/0.13.5...0.14.0 https://github.com/mozilla/loop-client/compare/0.14.0...0.15.0 TAGS https://github.com/mozilla/loop-client/releases/tag/0.15.0 https://github.com/mozilla/loop-client/commit/d706753dbcacfe17081d8c04b54652dbee36302f CHANGELOG 0.15.0 (2015-03-09) ------------------- - Bug 1047040 - Add browser-specific graphic of GUM prompt to the media-wait message - Bug 1131550 - Loop-client extraction script should preserve locale information when importing m-c changes - Bug 1135133 - Loop-client extraction script should support pulling from different repositories/branches - Bug 1137469 - If an uncaught exception occurs whilst processing an action, the dispatcher can fail, rendering parts of Loop inactive - Bug 1131568 - Update the OpenTok SDK to version 2.5.0
deploy-tix will make multiple calls to github API. You're allowed up to 60 calls / hour without authentication, but you'll soon run out!
Instead, create an access token from your github home page. Go to: #. Settings > Applications > Generate New Token #. Create an environment variable 'ACCESS_TOKEN' or enter it into the config.py:
$ export ACCESS_TOKEN=<your_access_token_here>
$ make build $ source ./venv/bin/activate
(venv)$ ticket
Usage: ticket [args..] [options]
-h, --help show this help message and exit
-o REPO_OWNER, --repo-owner REPO_OWNER Example: mozilla-services (default: mozilla-services)
-r REPO, --repo REPO Example: loop-server (default: None)
-e ENVIRONMENT, --environment ENVIRONMENT Example: STAGE, PROD (default: STAGE)
-u BUGZILLA_USERNAME, --bugzilla-username BUGZILLA_USERNAME (default: None)
-p BUGZILLA_PASSWORD, --bugzilla-password BUGZILLA_PASSWORD (default: None)
-z, --bugzilla-prod Add this option, and you'll post to bugzilla prod (default: False)Post to bugzilla-dev
$ ticket -o mozilla-services -r loop-server -e STAGE -u johnny@quest.com -p password123
Post to bugzilla (add -z option)
$ ticket -o mozilla-services -r loop-server -e STAGE -u johnny@quest.com -p password123 -z