-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(pipelineRef): add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger #4816
fix(pipelineRef): add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger #4816
Conversation
…to PipelineRefTrigger
this fix needs to be backported to 1.36.x and 1.35.x |
Tests please. |
sure, let me add test around it |
...sql/src/main/kotlin/com/netflix/spinnaker/orca/sql/PipelineRefTriggerDeserializerSupplier.kt
Show resolved
Hide resolved
@jasonmcintosh I added tests and PR is ready for review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the tests are a TOUCH more complicated than they need to be but work well for waht this is. Looks like this should fix dealing with the resolved expected artifacts...
NOT sure we won't hit more cases but... kinda hoping we can keep this as small as possible... |
@Mergifyio backport release-1.36.x release-1.35.x |
✅ Backports have been created
|
…to PipelineRefTrigger (#4816) * fix(pipelineRef): add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger * fix(pipelineRef): add tests around PipelineRefTrigger --------- Co-authored-by: Jason <[email protected]> (cherry picked from commit 3c65fe0)
…to PipelineRefTrigger (#4816) * fix(pipelineRef): add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger * fix(pipelineRef): add tests around PipelineRefTrigger --------- Co-authored-by: Jason <[email protected]> (cherry picked from commit 3c65fe0)
…to PipelineRefTrigger (#4816) (#4817) * fix(pipelineRef): add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger * fix(pipelineRef): add tests around PipelineRefTrigger --------- Co-authored-by: Jason <[email protected]> (cherry picked from commit 3c65fe0) Co-authored-by: Edgar Garcia <[email protected]>
…to PipelineRefTrigger (#4816) (#4818) * fix(pipelineRef): add resolvedExpectedArtifacts from pipelineTrigger to PipelineRefTrigger * fix(pipelineRef): add tests around PipelineRefTrigger --------- Co-authored-by: Jason <[email protected]> (cherry picked from commit 3c65fe0) Co-authored-by: Edgar Garcia <[email protected]>
Spel expressions with the function
#triggerResolvedArtifact
are throwing an evaluation error when pipelineRef feature is enabled in Orca. See: spinnaker/spinnaker#6993The error happens because when we transform a PipelineTrigger into a PipelineRefTrigger we are not populating the
resolvedExpectedArtifacts
. As theresolvedExpectedArtifacts
is empty the Spel function#triggerResolvedArtifact
is not able to collect the artifact we want.This small code change fix the issue.