Closed
Bug 997183
Opened 11 years ago
Closed 10 years ago
MockCommand doesn't pay attention to Builder env variables
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
Details
I noticed this while doing a staging release. We set BUILDBOT_CONFIGS and BUILDBOTCUSTOM as builder level properties, but they're not carried forward into the mock environment. This means that things like update verify don't work correctly in staging.
| Reporter | ||
Comment 1•11 years ago
|
||
I tried this to fix it, but it didn't work: https://github.com/bhearsum/buildbotcustom/commit/215d7bfc6f737bb2e52a8c9f541d69e3dc89cba1
I don't have more time to poke at it, so I'm working around it by changing the hardcoding in chunked_verify.sh =\
| Reporter | ||
Comment 2•11 years ago
|
||
I added a note about this to https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Staging_Specific_Notes#Staging_specific_preparation
Comment 3•10 years ago
|
||
docker wins!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•