st-an builds incorrectly use .linux64 and .macosx64 routes

RESOLVED FIXED

Status

task
RESOLVED FIXED
4 years ago
2 years ago

People

(Reporter: mshal, Assigned: mshal)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

The static analysis build configurations inherit from the base linux/mac configurations, but the base linux/mac configs specify some buildbot.* routes. For example, linux64_clobber.yml has:

  routes:
    - 'index.buildbot.branches.{{project}}.linux64'
    - 'index.buildbot.revisions.{{head_rev}}.{{project}}.linux64'

Since the st-an builds inherit this file in addition to providing their own routes, they have multiple buildbot routes:

    "index.buildbot.branches.mozilla-central.linux64",
    "index.buildbot.revisions.None.mozilla-central.linux64",
    "index.buildbot.branches.mozilla-central.linux64-st-an",
    "index.buildbot.revisions.None.mozilla-central.linux64-st-an",

The st-an builds shouldn't be publishing to .linux64 / .macosx64

Although I'd like to remove these buildbot routes entirely at some point, we aren't ready to do so yet.
This was a bit annoying to refactor since some of the intermediate files in the hierarchy are also themselves tasks (eg: opt_linux64_clobber.yml is referenced from try/job_flags.yml and also inherited by other tasks). If there is a better way to do this, please let me know!
Assignee: nobody → mshal
Attachment #8673799 - Flags: review?(garndt)
I was using this patch to help debug taskcluster-graph - it stubs out all of the variable things (like taskIds and dates and such), so that you can diff the output from './mach taskcluster-graph ...'.

Is there a better way to do that? Some sort of dry-run capability or something? I wanted to make sure I wasn't deleting routes or changing the build configuration inadvertently.
Flags: needinfo?(garndt)
Blocks: 1212942
Comment on attachment 8673799 [details] [diff] [review]
0001-Bug-1214758-remove-.linux64-.macosx64-routes-from-st.patch

Review of attachment 8673799 [details] [diff] [review]:
-----------------------------------------------------------------

This looks good to me.
Attachment #8673799 - Flags: review?(garndt) → review+
(In reply to Michael Shal [:mshal] from comment #2)
> Created attachment 8673801 [details] [diff] [review]
> debug-tc.patch
> 
> I was using this patch to help debug taskcluster-graph - it stubs out all of
> the variable things (like taskIds and dates and such), so that you can diff
> the output from './mach taskcluster-graph ...'.
> 
> Is there a better way to do that? Some sort of dry-run capability or
> something? I wanted to make sure I wasn't deleting routes or changing the
> build configuration inadvertently.

I'm not aware of a better way, and this is neat.  I usually just do a diff and ignore the date related changes although this one definitely reduces a lot of the noise.

I think we need to determine the longevity of the mach command and if it's worth investing in some of these niceties that definitely come in useful.  Thanks for attaching the patch so I could take a look!
Flags: needinfo?(garndt)
https://hg.mozilla.org/mozilla-central/rev/f1a04b2e2baf
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Product: TaskCluster → Firefox Build System
You need to log in before you can comment on or make changes to this bug.