Details
-
Suggestion
-
Resolution: Won't Fix
Description
BCLOUD-16728 implemented the ability to disable artifact downloads for a step.
I have multiple artifacts generated from previous steps and then a step that only requires access to a small subset of those artifacts. I would like to be able to have fine grained control over the artifacts that are downloaded.
I would suggest it uses the same globbing as used to save artifacts.
For example, this example pipeline has 3 stages, where a step requires artifacts from the step before, but not any further back. It contains suggested new keys under the step:artifacts:download_filter key:
'example-pipeline':
- step:
name: Step A
script:
- do_stuff.a
artifacts:
paths:
- artifacts_a/**
- step:
name: Step B
script:
- do_stuff.b
artifacts:
download_filter:
- artifacts_a/**
paths:
- artifacts_b/**
- step:
name: Step C
script:
- do_stuff.c
artifacts:
download_filter:
- artifacts_b/**
paths:
- artifacts_c/**