Closed Bug 1116750 Opened 8 years ago Closed 7 years ago
Forcing a repack builder requires to set the "specify script
_repo _revision" value
We had a failed repack in Firefox 35.0b8 build 1 (hg timeout) Usually, when this happens, we re-trigger the job but forcing the builder ended with this error: KeyError: 'script_repo_revision' + releaseTag= As it is now, to re-start a repack, we need to specify the script_repo_version value manually. We need to figure out how to do this automatically.
Trying this in staging - set the script_repo_revision on the desktop builder, rather than the scheduler. Mobile l10n already has it set on the builder.
Comment on attachment 8652148 [details] [diff] [review] [buildbotcustom] Set property on the builder The script_repo_revision property doesn't have a useful affect on an Aggregating scheduler, but it does work on the builder for scheduled and rebuilds. I can't find any reason why this was removed in bug 607392.
To clarify the diff, this sets script_repo_revsion in the set of properties for both firefox and fennec, where previously it was only set for fennec.
Assignee: nobody → nthomas
Note to self - update https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Tagging_through_Signing#Chunked_repacks when this lands
Attachment #8652148 - Flags: review?(bhearsum) → review+
Comment on attachment 8652148 [details] [diff] [review] [buildbotcustom] Set property on the builder http://hg.mozilla.org/build/buildbotcustom/rev/3af7c68dfe12
Attachment #8652148 - Flags: checked-in+
Rail used this in production today.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
\o/ /me throws away special wand
You need to log in before you can comment on or make changes to this bug.