Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
landing soon: change to how decision tasks are triggered
1 view
Skip to first unread message
Dustin Mitchell
Mar 6, 2019, 7:40:46 PM3/6/19
to Sheriffs, Engineering, Mozilla, tools-taskcluster
Details: https://bugzilla.mozilla.org/show_bug.cgi?id=1526979
I would like to land a change which should be fairly transparent, but could
go wrong. I'd like to do so next Tuesday around 9am pacific. The landing
process will require a brief tree closure (just a minute or two) followed
by a few pushes then a slightly longer closure to monitor those pushes and
make sure they're looking OK. If so, reopen. If not, rollback and
reopen. I'd like to apply this just for autoland and inbound. If all goes
well, I can apply for other branches later (with less advance preparation).
Please let me know if this is a good plan, or if you'd like me to adjust
anything.
Briefly, the change replaces the mozilla-taskcluster service, which polls
hg repositories and creates decision tasks when changes are discovered;
with a Taskcluster hook that runs immediately when a change is made, based
on a Pulse message. The externally-visible behavior won't change, but it
gets a bunch of advantages including better visibility into decision-task
issues, faster decision task startup, and getting rid of an old and very
confusing service.
This will eventually apply to all hg.mozilla.org repos, including nss and
comm-central.
Dustin
I would like to land a change which should be fairly transparent, but could
go wrong. I'd like to do so next Tuesday around 9am pacific. The landing
process will require a brief tree closure (just a minute or two) followed
by a few pushes then a slightly longer closure to monitor those pushes and
make sure they're looking OK. If so, reopen. If not, rollback and
reopen. I'd like to apply this just for autoland and inbound. If all goes
well, I can apply for other branches later (with less advance preparation).
Please let me know if this is a good plan, or if you'd like me to adjust
anything.
Briefly, the change replaces the mozilla-taskcluster service, which polls
hg repositories and creates decision tasks when changes are discovered;
with a Taskcluster hook that runs immediately when a change is made, based
on a Pulse message. The externally-visible behavior won't change, but it
gets a bunch of advantages including better visibility into decision-task
issues, faster decision task startup, and getting rid of an old and very
confusing service.
This will eventually apply to all hg.mozilla.org repos, including nss and
comm-central.
Dustin
Dustin Mitchell
Mar 7, 2019, 9:40:57 AM3/7/19
to Sheriffs, Engineering, Mozilla, tools-taskcluster
*UPDATE:* Per discussion with Sebastian, it would be better to make this
change today than next Tuesday, to avoid the soft code freeze. It still
only affects inbound and autoland, so today's beta is unaffected, as are
nss and comm-central.
Dustin
change today than next Tuesday, to avoid the soft code freeze. It still
only affects inbound and autoland, so today's beta is unaffected, as are
nss and comm-central.
Dustin
Dustin Mitchell
Mar 7, 2019, 11:09:44 AM3/7/19
to Sheriffs, Engineering, Mozilla, tools-taskcluster
This landed successfully, with CoT passing and everything.
I'll land on other branches next week, with somewhat less fanfare. The
only branch that will need more fanfare is try, as once the landing is
complete, try pushes with a parent before Feb 4 will no longer build. I'll
send out some communication about that at the time (the fix involves
cherry-picking a few csets).
Dustin
I'll land on other branches next week, with somewhat less fanfare. The
only branch that will need more fanfare is try, as once the landing is
complete, try pushes with a parent before Feb 4 will no longer build. I'll
send out some communication about that at the time (the fix involves
cherry-picking a few csets).
Dustin
0 new messages