When hacking on `taskgraph`, we find it useful to run [taskgraph-gen and taskgraph-diff](https://hg.mozilla.org/build/braindump/file/tip/taskcluster/taskgraph-diff). These build various release graphs and on-push graphs on various branches. By generating these graphs against both a clean and patched revision, we can diff to pinpoint what we're changing. A while back, I wondered if we could generate these graphs whenever the taskgraph changes. We could then diff against the previous indexed taskgraph generation task's artifacts. These diffs would likely be more useful to humans than automation.
Bug 1640902 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When hacking on `taskgraph`, we find it useful to run [taskgraph-gen and taskgraph-diff](https://hg.mozilla.org/build/braindump/file/tip/taskcluster/taskgraph-diff). These build various release graphs and on-push graphs on various branches. By generating these graphs against both a clean and patched revision, we can diff to pinpoint what we're changing. A while back, I wondered if we could generate these graphs whenever the taskgraph changes. We could then diff against the previous indexed taskgraph generation task's artifacts. These diffs would likely be more useful to humans than automation. (Edit: We could, however, add some checks here to make sure that we don't see unexpected changes in the release graphs or on other branches.)
When hacking on `taskgraph`, we find it useful to run [taskgraph-gen and taskgraph-diff](https://hg.mozilla.org/build/braindump/file/tip/taskcluster/taskgraph-diff). These build various release graphs and on-push graphs on various branches. By generating these graphs against both a clean and patched revision, we can diff to pinpoint what we're changing. A while back, I wondered if we could generate these graphs whenever the taskgraph changes. We could then diff against the previous indexed taskgraph generation task's artifacts. These diffs would likely be more useful to humans than automation. (Edit: We could, however, add some checks here to make sure that we don't see unexpected changes in the release graphs or on other branches like Try.)