Closed Bug 1277837 Opened 8 years ago Closed 7 years ago

Tier-1 Taskcluster jobs shouldn't group themselves under [tc]

Categories

(Firefox Build System :: Task Configuration, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1386857

People

(Reporter: ted, Assigned: dustin)

References

Details

We replaced the Linux debug buildbot jobs with Taskcluster jobs recently. One quirky side effect I noticed today is that Taskcluster jobs still group themselves under `tc()`. This means that for Linux debug, even the build job will get collapsed into a `tc(+N)` group, which we don't do for any other platform where we build via buildbot. I think this is sort of confusing and we should fix it. We might want to preserve this for tier-2 build jobs until they get promoted to tier-1.

This happens in the base build task:
https://dxr.mozilla.org/mozilla-central/rev/4d63dde701b47b8661ab7990f197b6b60e543839/testing/taskcluster/tasks/build.yml#61

I don't know if that's easily overridable from other task definitions that inherit that.
According to this comment, a ? works:
https://dxr.mozilla.org/mozilla-central/source/testing/taskcluster/tasks/builds/mulet_linux.yml#49

Though it looks like most child build tasks specify groupSymbol anyway.. could probably just remove it from the base config.
Let's do this.. the tc(..) groups keep confusing people.
(In reply to Dustin J. Mitchell [:dustin] from comment #2)
> Let's do this.. the tc(..) groups keep confusing people.

Now that basically all of our Tier-1 jobs are in TC, there's no reason to keep this grouping.
Assignee: nobody → dustin
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Product: TaskCluster → Firefox Build System
You need to log in before you can comment on or make changes to this bug.