Yes, we can already use `--use-existing-tasks`: https://treeherder.mozilla.org/jobs?repo=try&revision=d963461ac8110f76c3f5b819a3fd9b70acb29402 . That seems to work great, but requires the flag be specified explicitly (might be forgotten) and only helps on try. I'm trying to capture a few performance concerns that have been raised recently: 1. Fenix developers can currently create a pull request and see their Fenix builds running after just a few minutes; on try, there's a significant delay if they forget --use-existing-tasks. 2. A local artifact build of geckoview often takes about 5 minutes, but we wait for 20 to 30 minutes for a geckoview artifact build on try (decision task, per-platform build task setup, geckoview archive creation) -- could we do better?
Bug 1882160 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Yes, we can already use `--use-existing-tasks`: https://treeherder.mozilla.org/jobs?repo=try&revision=d963461ac8110f76c3f5b819a3fd9b70acb29402 . That seems to work great, but requires the flag be specified explicitly (might be forgotten) and only helps on try. I'm trying to capture a few performance concerns that have been raised recently: 1. Fenix developers can currently create a pull request and see their Fenix builds running after just a few minutes; on try, there's a significant delay if they forget --use-existing-tasks. 2. A local artifact build of geckoview often takes about 5 minutes, but we wait for 20 to 30 minutes for a geckoview artifact build on try (decision task, per-platform build task setup for 4 platforms, geckoview archive creation) -- could we do better?