doing manual this cycle but be nice to have an option. jlund> Jordan Lund RyanVM: so this l10n bumper stuff. we normally trigger aforced bumper run after merges: 14:49:17 https://github.com/mozilla-releng/releasewarrior-2.0/blob/9b226e7b8207bf84be153b2063434c8b02d4107a/docs/mergeduty/howto.md#run-the-l10n-bumper 14:49:30 <RyanVM> yes 14:49:46 and we need to make sure it's done w/o DONTBUILD so we can gtb off that push 14:50:00 <•jlund> Jordan Lund I can modify the script to remove DONTBUILD from commit message. Not sure how many commits we do and where, nor how often that runs but I'll comment it out for the forced run that I do

Comment on attachment 8986202 [details] Bug 1469423 - add an option to let l10n-bumper trigger builds. https://reviewboard.mozilla.org/r/251616/#review257970 Looks good to me. Even though the "build" -> "dontbuild" storage is slightly confusing a bit, the logic makes sense. We'd need to update https://github.com/mozilla-releng/releasewarrior-2.0/blob/9b226e7b8207bf84be153b2063434c8b02d4107a/docs/mergeduty/howto.md#run-the-l10n-bumper to add the "--build" right?

Comment on attachment 8986202 [details] Bug 1469423 - add an option to let l10n-bumper trigger builds. https://reviewboard.mozilla.org/r/251616/#review257970 Yup, passing --build in addition to --ignore-closed-tree in the manual run after the merge from central should do it. Thanks for the review!

Pushed by jcristau@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/166bb5e00004 add an option to let l10n-bumper trigger builds. r=mtabara

https://github.com/mozilla-releng/releasewarrior-2.0/pull/154 is fixing the docs for the future.