Enable builds and tests runs for the 'cedar' project branch
Categories
(Release Engineering :: General, enhancement)
Tracking
(Not tracked)
People
(Reporter: mikedeboer, Assigned: mikedeboer)
References
Details
Attachments
(1 file)
Over at https://treeherder.allizom.org/#/jobs?repo=cedar you can see that no jobs are running for cedar yet, but I'd really to like to see our status.
Unsure if this is the cause of the problem, but in-tree taskcluster applies this filter to determine what jobs get run on cedar: https://hg.mozilla.org/mozilla-central/file/tip/taskcluster/taskgraph/target_tasks.py#l219
Comment 2•6 years ago
|
||
Also I don't see cedar listed on:
https://tools.taskcluster.net/index/gecko.v2
Comment 3•6 years ago
|
||
I'm not great with ci-admin/ci-configuration stuff yet, but I think we need to update https://hg.mozilla.org/build/ci-configuration/file/tip/projects.yml and then run the ci-admin tool against the new repo. :dustin, :aki, or :tomprince would likely know more in this area.
Assignee | ||
Comment 4•6 years ago
|
||
Dustin, is Justin right in comment 3 that this is what needs to be adjusted to make things work here? If not, can you perhaps point us in the right direction?
Thanks!
Comment 6•6 years ago
|
||
And you can make a phabricator request to do just that :)
Assignee | ||
Comment 7•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Comment 8•6 years ago
|
||
I backed this out for the moment since cedar is still a level-2 repository:
https://hg.mozilla.org/projects/cedar/json-repoinfo
once that's fixed (which the hg team will need to do) we can re-land this. Sorry for the confusion.
Comment 9•6 years ago
|
||
See-Also 1521806
Updated•6 years ago
|
Updated•6 years ago
|
Comment 10•6 years ago
|
||
https://hg.mozilla.org/build/ci-configuration/rev/2b9e4ff2aa09
Looking at the related bugs, it doesn't look like there is any reason for this to level 3. I simplified the commit to just enable on-push builds and landed it.
Comment 11•6 years ago
•
|
||
mozilla-taskcluster has been restarted to pick up this change, and no scope changes are required.
Description
•