Document global properties that affect all pipeline uploads to a build
Open
- Dominant language
- Ruby
- Stars
- 59
- Forks
- 313
- PR merge metrics
- No merged PRs in 30d
Description
We have a couple of global fields in the pipeline YAML: `env` and `agents`. These are saved on the build rather than just applying to the steps that are being uploaded.
Several times now customers have been surprised that these not only affect the steps in the current pipeline upload of steps, _but all subsequently uploaded steps too_.
e.g.
```
cat <
Contributor guide
Assessment
This issue has not been assessed yet.