Fix: trigger VPA pipeline on changes in .ci folder #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Add the
.ci
folder to the list of triggers for the VPA pipeline. My original intention with leaving this directory out was to avoid automatic pipeline runs when only the.ci
folder changed, as this would still use the old pipeline definitions and be therefore not really useful. However, it turns out that the concourse git resource filters out commits that don't match thepath
property entirely, such that even manual pipeline runs never see this commit.This is not what we want, therefore let's accept the inconvenience of unnecessary pipeline runs.
Special notes for your reviewer:
Release note: