Configure update jobs to not fetch from "-dev" balrog aliases

RESOLVED FIXED

Status

enhancement
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: kmoir, Assigned: jlorenzo)

Tracking

unspecified
Dependency tree / graph

Firefox Tracking Flags

(firefox58 fixed)

Details

Attachments

(3 attachments)

No description provided.
Assignee: nobody → jlorenzo
Attachment #8917759 - Attachment description: Bug 1407331 - Staging releases: Remove *-dev update channel → [gecko] Bug 1407331 - Staging releases: Remove *-dev update channel
Attachment #8917806 - Attachment description: Bug 1407331 - Staging releases: Remove *-dev update channel → [build/tools] Bug 1407331 - Staging releases: Remove *-dev update channel
Attachment #8917808 - Attachment description: Bug 1407331 - Staging releases: Remove *-dev update channel → [buildbot-configs] Bug 1407331 - Staging releases: Remove *-dev update channel
Attachment #8917808 - Attachment description: [buildbot-configs] Bug 1407331 - Staging releases: Remove *-dev update channel → Bug 1407331 - Staging releases: Remove *-dev update channel
Attachment #8917808 - Flags: review?(kmoir)
Comment on attachment 8917808 [details]
[buildbot-configs] Bug 1407331 - Staging releases: Remove *-dev update channel

https://reviewboard.mozilla.org/r/188762/#review194060
Attachment #8917808 - Flags: review?(kmoir) → review+
Comment on attachment 8917808 [details]
[buildbot-configs] Bug 1407331 - Staging releases: Remove *-dev update channel

https://hg.mozilla.org/build/buildbot-configs/rev/9fbe3214b75f
Attachment #8917808 - Flags: checked-in+
Comment on attachment 8917806 [details]
[build/tools] Bug 1407331 - Staging releases: Remove *-dev update channel

For the 3 patches, I looked up on both DXR[1][2]:
* aurora-dev
* beta-dev
* release-dev

After the patches are applied, there is no occurrence left.

I ran the changes against this staging release[3]. Things look good overall. The only remaining problem is: because Balrog has the production data, update verify tests are trying to download release that comes from a production watershed. Like Ben suggested, we can clean old releases from patcher config. But that's something to do in another bug.

[1] https://dxr.mozilla.org/build-central/source/
[2] https://dxr.mozilla.org/mozilla-central/source/
[3] https://tools.taskcluster.net/groups/L21PXX0GQ6KlI0MBG-ae-A
Attachment #8917806 - Flags: review?(bhearsum)
Comment on attachment 8917806 [details]
[build/tools] Bug 1407331 - Staging releases: Remove *-dev update channel

https://reviewboard.mozilla.org/r/188742/#review195492
Attachment #8917806 - Flags: review?(bhearsum) → review+
Comment on attachment 8917759 [details]
Bug 1407331 - Staging releases: Remove *-dev update channel

https://reviewboard.mozilla.org/r/188698/#review195494
Attachment #8917759 - Flags: review?(bhearsum) → review+
Johan can this bug be closed or is there additional work that is required to complete it?
Flags: needinfo?(jlorenzo)
Thanks for following up on this. The job is done on Jamun, but I think the patch needs to ride the trains. I initially wanted to make sure Jamun works fine before riding them. I don't mind landing the patch on central now, though.
Flags: needinfo?(jlorenzo)
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s 72ac12d0cb0b -d 0b2f0f688fe3: rebasing 428630:72ac12d0cb0b "Bug 1407331 - Staging releases: Remove *-dev update channel r=bhearsum" (tip)
merging testing/mozharness/configs/releases/dev_updates_firefox_beta.py
merging testing/mozharness/configs/releases/dev_updates_firefox_release.py
warning: conflicts while merging testing/mozharness/configs/releases/dev_updates_firefox_beta.py! (edit, then use 'hg resolve --mark')
warning: conflicts while merging testing/mozharness/configs/releases/dev_updates_firefox_release.py! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
Attachment #8917808 - Attachment description: Bug 1407331 - Staging releases: Remove *-dev update channel → [buildbot-configs] Bug 1407331 - Staging releases: Remove *-dev update channel
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fb90c2538141
Staging releases: Remove *-dev update channel r=bhearsum
Discussed offline: In order to prevent bad merges from m-c to jamun, we agreed to merge patches to the main repos.
Backed out in https://hg.mozilla.org/integration/autoland/rev/a1d57c259c8e for https://treeherder.mozilla.org/logviewer.html#?job_id=138502821&repo=autoland (at least I think that flavor of failure is the real one, and https://treeherder.mozilla.org/logviewer.html#?job_id=138502819&repo=autoland is not, not sure since neither one makes much sense from the patch)
Thank you for the backout. You're right, I cause that failure. Like Callek said offline, we've already seen somthing similar on the jamun testing branch. I had fixed it there [1], but I forgot to update mozreview :/. 

I just did. I triggered a try submission[2], just to make sure I don't blow up autoland once more. 

[1] https://hg.mozilla.org/projects/jamun/rev/cb1ba4ad960c#l1.17
[2] https://treeherder.mozilla.org/#/jobs?repo=try&revision=617e8a8d3570be22afa92b4119c02c54b8a6dafe
Try run passed. Re-landing.
Pushed by jlorenzo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bd87a65f05b0
Staging releases: Remove *-dev update channel r=bhearsum
https://hg.mozilla.org/mozilla-central/rev/bd87a65f05b0
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.