Closed Bug 1426115 Opened 8 years ago Closed 8 years ago

use DONTBUILD in tagging commit messages

Categories

(Release Engineering :: Release Automation, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bhearsum, Assigned: kmoir)

Details

Right now we end up triggering a full set of builds & tests for each tagging commit. There's no reason to do this!
On the other hand these pushes also contain version bump commits. I'd argue that the version bump commits should get full build and test coverage - they may uncover some weird behaviour.
Not all of them do - some only do tagging, eg: https://treeherder.mozilla.org/#/jobs?repo=maple&revision=6b743161ace68c59548c261f653602b34fc5dedf Perhaps we should do two pushes, and set DONTBUILD for tagging commits?
Probably because we explicitly set the next version and the bump was a noop. In real world situation we rarely push tag-only commits afaik.
Assignee: nobody → kmoir
bhearsum> rail-bbl: do you think we should WONTFIX https://bugzilla.mozilla.org/show_bug.cgi?id=1426115 (cc kmoir)? 12:15 PM <kmoir> yes I was just going to ask that 12:15 PM if it's not something we see in production, not sure if it's worth fixing 12:15 PM <bhearsum> yeah, agreed 12:16 PM i think we still might see the the double tagging on beta for devedition + firefox, not certain though...
Flags: needinfo?(rail)
KILLEMALL! :)
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(rail)
Resolution: --- → WONTFIX
We're going to see extra runs, since we're going to run version bumping for fennec, devedition, and firefox.
You need to log in before you can comment on or make changes to this bug.