Right now we are testing desktop builds in staging that don't have add-on signing enabled. This will allow add-on developers to test their code before release. In any case, the are currently named like this Linux x86-64 mozilla-beta no add-on signing build These builds will be used for testing eventually on m-b and m-r. Suggestions for builder names that will look acceptable in treeherder? Linux x86-64 mozilla-beta add-on signing disabled build Linux x86-64 mozilla-beta add-on developer build
Adding RyanVM for needinfo since he's good at naming things :-)
This is going to be just a new build or a full build + tests?
A new build. However, we'll be running some tests on it, see https://bugzilla.mozilla.org/show_bug.cgi?id=1184214#c0
My main concern is using names that can be easily parsed by Treeherder buildbot job regex. And we'll want to make sure that the test runs use a similar convention so that they can be identified based on what build they're running on. Ed, do the names in comment 0 look OK to you? We can sort out the TH presentation in a separate bug.
Flags: needinfo?(ryanvm) → needinfo?(emorley)
If we';re running builds+tests, I guess this needs to be a new row in Treeherder, so we need to treat this using the categories we use for opt vs debug vs asan etc. So as long as there's some substring we can pull out, that doesn't clash with the ones here: https://github.com/mozilla/treeherder/blob/master/treeherder/etl/buildbot.py#L385-L407 ...then it should be fine.
I'm going to call them add-on-devel builds. It is short enough that it doesn't hit the 30 char limit when the other platform and branch are added to the string.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.