Migrate taskcluster_yml_validator to community taskcluster deployment
Categories
(Taskcluster :: Operations and Service Requests, task)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: owlish)
References
Details
This uses TC for its CI and also accesses schemas.taskcluster.net
I'll have a closer look regarding
- any necessary updates to CI
- what schemas it accesses and how to access those in a rootUrl-dependent way
|
Reporter | |
Comment 1•5 years ago
|
||
|
|
Reporter | |
Updated•5 years ago
|
|
Assignee | |
Comment 2•5 years ago
•
|
||
✅ taskcluster.yml is v1
✅ Checked Roles and Scopes - seems to be no special scopes or roles
✅ https://github.com/mozilla/community-tc-config/pull/41/files add config
✅ https://github.com/marco-c/taskcluster_yml_validator/pull/28 PR to the repo
|
|
Reporter | |
Comment 3•5 years ago
|
||
PSA: The existing (https://taskcluster.net) deployment will be shut down a week from today, on November 9. After that point, any CI not migrated to the new community cluster will stop functioning. The TC team is ready and eager to help get everything migrated by that time, but the deadline is firm.
Apologies for failing to communicate this as broadly and loudly as necessary, and for the bugspam now.
|
||
Comment 4•5 years ago
|
||
This is done: https://github.com/marco-c/taskcluster_yml_validator/pull/30.
|
|
||
Comment 5•5 years ago
|
||
Actually, the Taskcluster integration is working on PRs, but not on pushes: https://github.com/marco-c/taskcluster_yml_validator/commits/master.
|
|
||
Comment 6•5 years ago
|
||
Also strange: when I merged the PR, Taskcluster triggered a new task group on https://github.com/marco-c/taskcluster_yml_validator/pull/30, which failed as the branch had been deleted.
|
|
||
Comment 7•5 years ago
|
||
(In reply to Marco Castelluccio [:marco] from comment #5)
Actually, the Taskcluster integration is working on PRs, but not on pushes: https://github.com/marco-c/taskcluster_yml_validator/commits/master.
After a while, it was triggered. So the only remaining problem is the one from comment 6.
|
|
Reporter | |
Comment 8•5 years ago
|
||
SimonSapin also reported some delays in events -- it looks like things are a little choked up within GitHub, but hopefully smoothing out now. Who knows, maybe related to the Azure outage overnight?
Regarding comment 6, that is probably because there's no conditional on "action" in https://github.com/marco-c/taskcluster_yml_validator/blob/master/.taskcluster.yml, so it reacts to the "pull_request" event with action: closed.
|
|
||
Comment 9•5 years ago
|
||
(In reply to Dustin J. Mitchell [:dustin] (he/him) from comment #8)
Regarding comment 6, that is probably because there's no conditional on "action" in https://github.com/marco-c/taskcluster_yml_validator/blob/master/.taskcluster.yml, so it reacts to the "pull_request" event with
action: closed.
This never happened before though, in none of our projects (and none has a conditional on "action").
|
|
Reporter | |
Comment 10•5 years ago
|
||
I suspect it's always happened, intermittently depending on when the branch was deleted, and maybe just the extra scrutiny today made it visible. At any rate, as written that .taskcluster.yml should run every time a PR is closed, and if it doesn't that's a bug in tc-github.
|
|
||
Comment 11•5 years ago
|
||
That's possible, anyway I guess we can call this fixed.
Description
•