527996 - Do a sendchange to trigger unittest runs on geriatric machines

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

We need to do sendchanges from our regular buildbot masters to out geriatric master.  This bug tracks the work on getting the changes to buildbot-configs and buildbotcustom working.

Comment 1

[John Ford [:jhford] CET/CEST Berlin Time]

Attachment: buildbot-configs patch v1

This patch adds the needed changes for buildbot-configs to send the sendchange

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

Attachment: buildbotcustom patch v1

This patch adds the needed factory and generateBranchObjects logic to get this working.  Because we need to run jobs based on cpu and os type, we can't do exactly the same style of sendchange as talos and regular unit tests.

This patch does not have a staging component because it will never be run in staging.  I will test this patch in staging though.

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

Attachment: buildbot-configs patch v2

Tested in staging.  I ran this and apart from firewall issues blocking staging-master from sending a change to geriatric-master it worked.  There are still some issues slave-side about what to do with the packageUrl that I am passing but they can be worked out on the geriatric-master side

Comment 4

[John Ford [:jhford] CET/CEST Berlin Time]

Attachment: buildbotcustom patch v2

matching buildbotcustom patch

Comment 5

[Aki Sasaki (not active)]

Comment on attachment 412890 [details] [diff] [review]
buildbot-configs patch v2

Arrr! plus

Comment 6

[Aki Sasaki (not active)]

Comment on attachment 412891 [details] [diff] [review]
buildbotcustom patch v2

http://hg.mozilla.org/build/buildbotcustom/rev/d88acc26b73d

Comment 7

[Aki Sasaki (not active)]

Comment on attachment 412890 [details] [diff] [review]
buildbot-configs patch v2

http://hg.mozilla.org/build/buildbot-configs/rev/1bc1d6b84f78

Comment 8

[John Ford [:jhford] CET/CEST Berlin Time]

This is working in production and is triggering builds.