pipelineID is not resolved for existing pipeline when multiple pipeline stages are used #84
Labels
Backend-Spinnaker
The issue is related to the built-in Spinnaker Backend
bug
Something isn't working
save
Related to "shore save"
Pre Requisites
Description
While rendering a nested pipeline If one of the pipeline stage is a nested pipeline and another refers to an existing pipeline. The spinnaker pipeline id for the existing pipeline stage is not resolved. This is due to faulty check that skips the id resolution due to this check (
shore/pkg/backend/spinnaker/backend.go
Line 751 in 567fcf5
For example: In the nested pipeline in the image below (which is linked by the main application pipeline), the Redner stage refers to an existing pipeline while the Deploy stage that follows it is a nested pipeline. In the second image you can see that shore did not resolve the id of the Render pipeline (which was set to null).
Pipeline line Is was not resolved instead set to null.
Steps to Reproduce
shore/pkg/backend/spinnaker/backend_test.go
Line 834 in 567fcf5
shore/pkg/backend/spinnaker/backend.go
Line 154 in 567fcf5
Expected behavior:
The pipeline stage pointing to an existing should have have pipeline id resolved.
Actual behavior:
The pipeline stage pointing to an existing should have have pipeline id resolved to null.
Reproduces how often:
100%
Versions
Additional Information
The text was updated successfully, but these errors were encountered: