Closed Bug 1269911 Opened 8 years ago Closed 8 years ago

beta and release CI builds should clobber per-checkin

Categories

(Release Engineering :: Release Automation: Other, defect)

defect
Not set
normal

Tracking

(firefox46 fixed, firefox47 fixed, firefox48 fixed, firefox49 fixed)

RESOLVED FIXED
Tracking Status
firefox46 --- fixed
firefox47 --- fixed
firefox48 --- fixed
firefox49 --- fixed

People

(Reporter: jlund, Assigned: jlund)

References

Details

Attachments

(1 file)

Assignee: nobody → jlund
Comment on attachment 8748396 [details]
MozReview Request: Bug 1269911 - beta and release CI builds should clobber per-checkin, r?rail

https://reviewboard.mozilla.org/r/50261/#review47119
Attachment #8748396 - Flags: review?(rail) → review+
Comment on attachment 8748396 [details]
MozReview Request: Bug 1269911 - beta and release CI builds should clobber per-checkin, r?rail

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/50261/diff/1-2/
Comment on attachment 8748396 [details]
MozReview Request: Bug 1269911 - beta and release CI builds should clobber per-checkin, r?rail

I guess once a request is r+, mozreview doesn't reset it after pushing a new diff.

anyway, I updated the patch to only force clobber on actual release platforms: https://reviewboard.mozilla.org/r/50261/diff/1-2/
Attachment #8748396 - Flags: review+ → review?(rail)
Comment on attachment 8748396 [details]
MozReview Request: Bug 1269911 - beta and release CI builds should clobber per-checkin, r?rail

https://reviewboard.mozilla.org/r/50261/#review47263
Attachment #8748396 - Flags: review?(rail) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/60ce6cc4da0665503d9f9f5f66c4ddd9474228ea
Bug 1269911 - beta and release CI builds should clobber per-checkin, r=rail
https://hg.mozilla.org/mozilla-central/rev/60ce6cc4da06
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Needs uplifting to beta & release, right ?
Flags: needinfo?(jlund)
whoops, forgot to update tracking flags
Flags: needinfo?(jlund)
You need to log in before you can comment on or make changes to this bug.