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 levareging 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
Bug 1601928 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
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