Giters

spinnaker / roer

A thin Spinnaker CLI

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Pipeline doesn't inherit template's 'Configuration' step artefacts and trigger

dstrychalski opened this issue · comments

commented

Pipeline created from a template (both UI or via API) doesn't inherit S3 artefacts and trigger defined in the first 'Configuration' step in the template

commented

Does your pipeline app config have something like this defined?

configuration:
  inherit:
    - expectedArtifacts
    - concurrentExecutions
    - triggers
    - parameters

Preceding that section:

---
schema: "1"
pipeline:
  application: exampleapp
  id: exampleapp-deploy-to-dev
  name: deploy-to-dev
  owner: you@example.com
  template:
    source: spinnaker://deploy-to-dev-template
commented

I presume you refer to a pipeline config yaml. When deploying a pipeline with Roer using updated with configuration inherit section pipeline config I get the following error....

DEBU[0000] Reading config file=pipeline-config-test.yml
DEBU[0000] getting url url="https://spinnaker-api.../applications/someApp/pipelineConfigs/testing-cofing-inherit"
DEBU[0000] Response body= status=200
DEBU[0000] saving pipeline url="https://spinnaker-api..../pipelines"
DEBU[0001] Response body="{"error":"Bad Request","exception":"com.netflix.spinnaker.gate.controllers.PipelineController$PipelineException","message":"failed rendering jinja template","status":400,"timestamp":1538661534706}" status=400
FATA[0001] saving pipeline config: plan request failed

Although through API it works fine when without configuration section. I suspect Orca that needs fixing as after last month Spinnaker update to 1.9.3 I started seeing similar error in Deck (UI) when saving a parametrized pipeline created from a managed template.