VOOZH about

URL: https://phabricator.wikimedia.org/T397089

⇱ ⚓ T397089 scap backport should warn if it knows it will take a long time


Maniphest T397089

scap backport should warn if it knows it will take a long time
Closed, ResolvedPublic

Description

Something that came up whilst doing the UTC afternoon backport deployment window: It would be great to flag whether a commit will require a CDB rebuild, which is painful

The ideal would be to warn folks before merges a patch that they're in for a long deployment. This could be tricky/impossible to do deterministically.

But as soon as scap knows that we're going to do a full image rebuild, warning the users would be great.

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
backport: Warn when a l10n-touching change is backportedrepos/releng/scap!1187dancymaster-I8eff33db223af1cf61d5a0ddd912b602e3d0864emaster
Customize query in GitLab

Event Timeline

Comment Actions

But as soon as scap knows that we're going to do a full image rebuild, warning the users would be great.

Do you mean writing a (likely to be overlooked) line of log output while is running, or do you mean an interactive warning which requires the deployer to respond?

Comment Actions

Do you mean writing a (likely to be overlooked) line of log output while is running, or do you mean an interactive warning which requires the deployer to respond?

More the latter. Ideally, this is a pre-merge signal to the deployer like "This might take a while. Bring a Good Book."

In the case where the deployer is experienced, they can optimize the deployment window to get as many patches deployed as possible.

In the case where the deployer is inexperienced, they've been primed to expect a significantly-longer-than-usual deployment process.

This could be tricky/impossible to do deterministically.

AIUI there's really only one way to be 100% sure and that's immediately after we've run the maintenance script during but that we might be able to guess by checking whether the patch modifies files in the directory. We could, therefore, guess and flag pre-merge and then notify when we've run the maintenance script.

dancy changed the task status from Open to In Progress.May 14 2026, 7:43 PM
dancy claimed this task.
dancy triaged this task as High priority.
Comment Actions

Deployed in scap 4.266.0

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits