| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
Add a security release note for the "credentials leak on ansible
unreachable error despite no_log" story. It's added to an existing
file so that it will appear in the 3.1.0 section.
Change-Id: I1060a964cad9863ce24abe830622370a3dbfbf80
Story: #2002177
Task: #22238
|
| |
|
|
|
|
|
|
|
|
|
| |
It's added to an existing file so that it will appear in the 3.1.0 section.
The overridable matcher note is changed to an upgrade note since it may
require changes.
And tidy up some other notes.
Change-Id: Ib049679f7df4424e43508a96096acecc6722f606
|
|
|
Files and irrelevant-files don't behave in the way people intuitively
expect. If a job or template has an irrelevant-files matcher, it's not
possible to alter its set of irrelevant-files in a project-pipeline
variant.
This changes them to be treated as overwriteable attributes and evaluated
after branch-matching variants are combined.
* Files and irrelevant-files are overwritten, so the last value
encountered when combining all the matching variants (looking only at
branches) wins.
* It's possible to both reduce and expand the scope of jobs, but the
user may need to manually copy values from a parent or other variant
in order to do so.
* It will no longer be possible to alter a job attribute by adding a
variant with only a files matcher -- in all cases files and
irrelevant-files are used solely to determine whether the job is run,
not to determine whether to apply a variant.
See http://lists.openstack.org/pipermail/openstack-dev/2018-May/130074.html
and http://lists.zuul-ci.org/pipermail/zuul-discuss/2018-May/000397.html
for further context.
Change-Id: I7b619df10c0896e696e065cb093d4e11911d3ce1
|
