Open Bug 1695018 Opened 3 years ago Updated 10 months ago

taskgraph changes to support comm-central as single repo


(Firefox Build System :: Task Configuration, task, P3)



(firefox89 affected)

89 Branch
Tracking Status
firefox89 --- affected


(Reporter: rjl, Assigned: rjl)


(Blocks 1 open bug)



(2 files)

Quick background:
Bug 1666242 is a project to convert the 2-repo setup for building Thunderbird to a single repository setup. The new repo could be considered a fork of mozilla-central.

This bug is to track changes to mozilla-central taskgraph code. For the most part it's expected that these changes will simplify the existing code.

For example, comm_head_repository and related parameters will no longer be needed and can be removed. The same goes for the comm-checkout run-task parameter.

The sparse-profile attribute does not allow for profiles to be located in
directories other than build/sparse-profiles/. Adding an optional prefix
attribute will allow for a future one-repository setup for Thunderbird development
to define sparse profiles to meet the projects needs.
The known use cases are for decision tasks and toolchain build tasks.

Pushed by
Add sparse-profile-prefix to run-task schema. r=taskgraph-reviewers,aki
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 89 Branch
Keywords: leave-open
Resolution: FIXED → ---
Pushed by
Allow "sparse-profile-prefix" on toolchain tasks. r=taskgraph-reviewers,jmaher

The leave-open keyword is there and there is no activity for 6 months.
:ahal, maybe it's time to close this bug?

Flags: needinfo?(ahal)

Assuming more work is still needed here.

I just wanted to call out Releng's vague plans w.r.t to taskgraph. We're starting to make the version of taskgraph in mozilla-central depend on the standalone one:

(Which is currently on pypi and vendored into m-c)

We're slowly moving the bits of gecko_taskgraph that make sense into the standalone version. The bits that don't make sense will remain in mozilla-central. I don't think comm-central needs to take this approach now, but it might be something worth working towards longer term (depend only on the standalone taskgraph and leave Gecko taskgraph out of it). But if there are still lots of things comm-central has in common with gecko_taskgraph, it can remain as a consumer.

Either way starting to have a dedicated comm_taskgraph module sounds like the way to go.

Flags: needinfo?(ahal)

Please keep this open, I will be picking this up again in the coming weeks.

The leave-open keyword is there and there is no activity for 6 months.
:ahal, maybe it's time to close this bug?
For more information, please visit auto_nag documentation.

Flags: needinfo?(ahal)
Assignee: nobody → rob
Flags: needinfo?(ahal)
Keywords: leave-open
Severity: -- → N/A
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.