summaryrefslogtreecommitdiff
path: root/.flake8
diff options
context:
space:
mode:
authorScott Wittenburg <scott.wittenburg@kitware.com>2023-03-08 09:38:07 -0700
committerGitHub <noreply@github.com>2023-03-08 09:38:07 -0700
commit4a9ffdcfa28046589eeee86aa47f16624c02d790 (patch)
treee2c8c15735563a6745d1c6ade166e19a49d84578 /.flake8
parent22d4e7903719b8f4039ea1875e15bd0bf3fe550b (diff)
downloadspack-4a9ffdcfa28046589eeee86aa47f16624c02d790.tar.gz
spack-4a9ffdcfa28046589eeee86aa47f16624c02d790.tar.bz2
spack-4a9ffdcfa28046589eeee86aa47f16624c02d790.tar.xz
spack-4a9ffdcfa28046589eeee86aa47f16624c02d790.zip
gitlab ci: Provide a knob to control untouched spec pruning (#35274)
When untouched spec pruning is enabled, specs possibly affected by a change cannot be pruned from a pipeline. Previously spack looked at all specs matching changed package names, and traversed dependents of each, all the way to the environment root, to compute the set of environment specs possibly affected by a change (and thus, not candidates for pruning). With this PR, when untouched spec pruning is enabled, a new environment variable can control how far towards the root spack traverses to compute the set of specs possibly affected by a change. SPACK_UNTOUCHED_PRUNING_DEPENDENT_DEPTH can be set to any numeric value before the "spack ci generate" command is called to control this traversal depth parameter. Setting it to "0" traverses only touched specs, setting it to "1" traverses only touched specs and their direct dependents, and so on. Omitting the variable results in the previous behavior of traversing all the way to the root. Setting it to a negative value means no traversal is done, and always yields an empty set of possibly affected specs (which would result in the max pruning possible).
Diffstat (limited to '.flake8')
0 files changed, 0 insertions, 0 deletions