Add release docs for artifact constraints bugfix (#270)

* Add release docs for artifact constraints bugfix See spinnaker/orca#4322 * Update content/en/docs/releases/next-release-preview/index.md Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com> Co-authored-by: David Byron <82477955+dbyron-sf@users.noreply.github.com>
spinnaker · Nov 7, 2022 · 5c0e902 · 5c0e902
1 parent 4da6879
commit 5c0e902
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/content/en/docs/releases/next-release-preview/artifact_constraints.png b/content/en/docs/releases/next-release-preview/artifact_constraints.png
diff --git a/content/en/docs/releases/next-release-preview/index.md b/content/en/docs/releases/next-release-preview/index.md
@@ -55,3 +55,11 @@ expression:
   do-not-eval-spel:
     enabled: true
 ```
+
+### Changes to the way artifact constraints on triggers work
+
+If you have a pipeline with multiple triggers using different artifact constraints/expected artifacts, these have for a while been evaluated in an unexpected matter.
+
+![Artifact constraints](artifact_constraints.png)
+
+In this example, even though each trigger has its own artifact(s) defined, when one of the artifacts is present, all of the defined artifact constraints on all triggers are evaluated. If _any_ of them is missing, the pipeline will not trigger. This is [fixed](https://github.com/spinnaker/orca/pull/4322) in Spinnaker 1.30 to only consider the artifacts that are defined on the triggered trigger. If you've relied on this bug, you'll need to add manually add all the artifact constraints to all triggers to replicate the previous behavior.