mobile projects: Restrict .cron.yml to main repos only
Categories
(Release Engineering :: General, enhancement)
Tracking
(Not tracked)
People
(Reporter: jlorenzo, Unassigned)
References
Details
In bug 1599128, I started to let Firefox CI configure Github forks, so I can make staging releases/nightlies more easily. Nightlies are made with taskcluster + taskgraph hooks, meaning we have a general hook that reads .cron.yml
and schedules graphs out of it. At the moment, general hooks schedules graphs off forks too. It's not a big issue, it just wastes some resources.
Let's improve the situation by leveraging the run-on-projects
feature to only automatically kick nightlies off main repos. This was suggested by :tomprince at [1]
Note: run-on-projects
doesn't prevent force hooks from being triggered. So, staging nightlies can still occur on forks, at will.
[1] https://phabricator.services.mozilla.com/D54960#inline-337635
Reporter | ||
Comment 1•4 years ago
|
||
Closing this bug as WONTFIX because we now have try_task_config.json
which allows people to run what's in .cron.yml
directly in a PR. I haven't manually triggered a cron hook since then \o/
Description
•