List view
Vague ideas for epics: * Finish off the Checks API support and announce a plan to drop status support * complete support for custom output from checks * rerun support (via actions) * Drop support for v0 .taskcluster.ymls * Other GH ideas we'd need to agree on (RFC) beforehand: * A way to remove the huge boilerplate .taskcluster.yml's in every repo * A way to call GitHub APIs from a task, with suitable scope-style control (allowing posting comments, pushing lint runs, etc.) * ..your ideas here
No due dateRationale: the current approach to service configuration was developed bit-by-bit and has a lot of misfeatures and weird behaviors as a result. This complexity has caused confusion, delays, and in a few cases minor outages. https://github.com/taskcluster/taskcluster/projects/8
No due dateGeneral theme: building new worker images, testing worker images, and rolling out new workers to as many users as possible should be automated in the community deployment.
Overdue by 4 year(s)•Due by November 13, 2020General theme: taskgraph should be the de-facto standard for decision-task based CI. * Identify and fix rough edges in existing taskgraph implementation * Implement platform support for otherwise-difficult bits of taskgraph * Improve documentation of taskgraph and refer to it from the Taskcluster documentation See https://trello.com/b/rofNrjvh/taskgraph-improvements for some notes on the topic by releng folks
Overdue by 4 year(s)•Due by January 22, 2021