Closed
Bug 940776
Opened 11 years ago
Closed 10 years ago
Infrastructure for 3rd-party builds, tests to react to 'build events'
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: taras.mozilla, Assigned: jonasfj)
Details
In order to make it easier to contribute to our build & test infrastructure we should make it easy to trigger own builds by listening to something like http://pulse.mozilla.org/ or tbpl logs. For example when a try build is submitted, it should be possible to receive notifications for every infrastructure step in order to trigger own tests, etc.
Assignee | ||
Comment 1•11 years ago
|
||
I've identified two infrastructure steps that produces reusable output: (A) Pushes of source code to some repository (produces source code to build), (B) Build of a push finished and tests ready to run (produces binaries to run) I've hooked into pulse, extracted pushes to try and requests to run unittests for try linux64, see demo: http://ec2-54-244-145-30.us-west-2.compute.amazonaws.com (Other tasks logs changes on other branches). This discards all messages about slaves starting, executing and finishing various steps. There is one minor annoyance/bug here, a try push with "try -b do -p all -u none -t none", won't produce any (B)-messages, because no tests are to be run. Short-term I think this is okay, long-term we might want to let try accept arguments like --thirdparty "<arbitrary string>" and then hack BuildBot to send a pulse message when a build with that argument is finished.
Assignee | ||
Comment 2•11 years ago
|
||
Update: Talked to catlee and we apparently can already add arguments to try, ie. a push with "try -b do -p all -u none -t none --hack blabla" works. Futhermore, such a push will also generated a change notification on the virtual branch: try-<platform>-(debug|opt)-unittest So forget the minor annoyance/bug I mentioned above, it just works :)
Assignee | ||
Comment 3•10 years ago
|
||
Fixed long time ago... it's called build-coordinator there is a broken deployment of it on heroku. I'll probably bring it to life again when integrating with pulse...
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•