Closed
Bug 1216311
Opened 9 years ago
Closed 9 years ago
date (staging release promotion) branch should use dev balrog server
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Assigned: jlund)
References
Details
Attachments
(1 file)
|
592 bytes,
patch
|
rail
:
review+
jlund
:
checked-in+
|
Details | Diff | Splinter Review |
14:18:22 <jlund> afaict, we are using the prod balrog server: 14:18:26 <jlund> https://dxr.mozilla.org/build-central/source/buildbot-configs/mozilla/production_config.py#46 14:18:31 <jlund> https://dxr.mozilla.org/build-central/source/tools/buildfarm/release/release-runner.py#262 14:18:33 <jlund> https://github.com/mozilla/releasetasks/search?utf8=%E2%9C%93&q=balrog_api_root 14:18:45 <jlund> (because date doesn't define its own, it uses production_config.py) 14:19:24 <jlund> from release-runner.log: 'env': { 'BALROG_API_ROOT': 'https://aus4-admin.mozilla.org/api',
|
Assignee | |
Comment 1•9 years ago
|
||
this is actually a no-op on dump_master which is expected as the only thing that will use date['balrog_api_root'] is releasetasks
Attachment #8675943 -
Flags: review?(rail)
|
||
Updated•9 years ago
|
Attachment #8675943 -
Flags: review?(rail) → review+
|
|
||
Updated•9 years ago
|
Assignee: nobody → jlund
Blocks: release-promotion
|
|
Assignee | |
Comment 2•9 years ago
|
||
Comment on attachment 8675943 [details] [diff] [review] 151019_balrog_dev_api_on_date-bbotcfgs.patch https://hg.mozilla.org/build/buildbot-configs/rev/c4ae6f2036cf
Attachment #8675943 -
Flags: checked-in+
|
||
Comment 3•9 years ago
|
||
In production: https://hg.mozilla.org/build/buildbot-configs/rev/c4ae6f2036cf
|
|
Assignee | |
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•