Bugzilla

Joel, would your team be best suited to address this bug? I discussed this at length with RelMan at our recent work week. It is one of the major things blocking adoption of Phab/Lando uplifts as the default, since in the new workflow each uplift is landed as a single push, instead of multiple uplifts being pushed after manually applying the patches in a local checkout. The increase in the number of pushes causes much higher load on CI given our current scheduling strategy, which is a risk for releases.

RelMan needs to be able to have full CI runs for things we release. We discussed a few options for ways we could make this happen:

- A cron which schedules full CI on release trains every N hours/minutes/etc, with only partial CI running on most pushes.
- Bugbug/autoland style scheduling on beta/release/etc. A hard blocker for this would be the ability to schedule a full CI run with a button on Treeherder.

If there are other options that we haven't considered it would be great to hear those too. We did consider attempting to implement coalescing uplifts together into a single landing, but it seems like this is more of a CI scheduling problem, and we would like to keep the uplift workflow as similar to the workflow for regular landings as possible.

Joel, would your team be best suited to address this bug? I discussed this at length with RelMan at our recent work week. It is one of the major things blocking adoption of Phab/Lando uplifts as the default, since in the new workflow each uplift is landed as a single push, instead of multiple uplifts being pushed at once after manually applying the patches in a local checkout. The increase in the number of pushes causes much higher load on CI given our current scheduling strategy, which is a risk for releases.

RelMan needs to be able to have full CI runs for things we release. We discussed a few options for ways we could make this happen:

- A cron which schedules full CI on release trains every N hours/minutes/etc, with only partial CI running on most pushes.
- Bugbug/autoland style scheduling on beta/release/etc. A hard blocker for this would be the ability to schedule a full CI run with a button on Treeherder.

If there are other options that we haven't considered it would be great to hear those too. We did consider attempting to implement coalescing uplifts together into a single landing, but it seems like this is more of a CI scheduling problem, and we would like to keep the uplift workflow as similar to the workflow for regular landings as possible.

Joel, would your team be best suited to address this bug? I discussed this at length with RelMan at our recent work week. It is one of the major things blocking adoption of Phab/Lando uplifts as the default, since in the new workflow each uplift is landed as a single push, instead of multiple uplifts being pushed at once after manually applying the patches in a local checkout. The increase in the number of pushes causes much higher load on CI given our current scheduling strategy, which is a risk for releases.

RelMan needs to be able to have full CI runs for things we release. We discussed a few options for ways we could make this happen:

- A cron which schedules full CI on release trains every N hours/minutes/etc, with only partial CI running on most pushes.
- Bugbug/autoland style scheduling on beta/release/etc. A hard blocker for this would be the ability to schedule a full CI run with a button on Treeherder.

If there are other options that we haven't considered it would be great to hear those too. We did consider attempting to implement coalescing uplifts together into a single landing in Lando, but it seems like this is more of a CI scheduling problem, and we would like to keep the uplift workflow as similar to the workflow for regular landings as possible.