965296 - Increase how often the vcs sync runs on git.m.o

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Ryan VanderMeulen [:RyanVM]]

We had a backout on the device-mako repo on Github that took an hour to propagate to git.m.o today. Hal says we can speed this up. Ideally, it would run around the same frequency that we run the bumper bot at.

Comment 1

[hwine]

At the moment, there is just one job for all b2g mirroring - both those that go to external/* and those that go to b2g/* on git.mozilla.org. That's > 280 repositories, and takes 1h45m to cycle (each needs to be polled).

As a first step, we'll split that job into 2 jobs. One for just the repos from github.com/mozilla-b2g (which go to b2g/* on git.mozilla.org), and leave the rest where they are. That will put 49 repos in the "faster cycle" category. These are the repos our devs change, so are more volatile and involved in backout activities such as led to comment 0.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

SGTM!

Comment 3

[hwine]

Attachment: move more volitile repositories to separate job

move all the less volatile jobs to a new jobstream

Comment 4

[hwine]

Comment on attachment 8367416 [details] [diff] [review]
move more volitile repositories to separate job

http://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-configs/rev/3d0f88519ab6

Comment 5

[hwine]

deployed to all production servers, now seeing 10-15 minute cycle time on repos mirrored to b2g/* (which are the ones ffos devs change directly)

Comment 6

[hwine]

new (slow) job deployed, and running successfully. Still about 1h40m cycle time, but they don't change very often at all.