Closed
Bug 797420
Opened 12 years ago
Closed 7 years ago
move talos suite information to somewhere it may be consumed
Categories
(Release Engineering :: General, defect, P3)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: k0scist, Unassigned)
Details
(Whiteboard: [configs])
Currently the talos suites run by buildbot and the associated arguments thereto are defined in buildbot-configs: http://hg.mozilla.org/build/buildbot-configs/raw-file/tip/mozilla-tests/config.py However, this is not particularly programmatically consumable. For the hoary details, see http://k0s.org/mozilla/hg/talosnames/file/277b167060e5/talosnames/api.py for what needs to be done to consume this. This should be consumable by trychooser and scripts such as talos names. Instead, this should be in some sort of data structure that may be easily consumed. JSON is probably a good choice. I would argue that this should go in mozilla-central so that it could ride the train, but anywhere web accessible is fine with me. I would probably put it in testing/talos/talos.json . Note that there has been some intention to fix this with mozharness. But the need for this transcends mozharness: it needs to be done anyway.
Comment 1•11 years ago
|
||
I think there's another bug for something like this, but I can't find it.
Priority: -- → P3
Whiteboard: [configs]
Comment 2•11 years ago
|
||
We have http://hg.mozilla.org/projects/cedar/file/default/testing/talos/talos.json for mozharness talos.
Assignee | ||
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
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
•