search

CircleCI-Public / continuation-orb

MIT License
12 stars 15 forks source link

Workflow did not get triggered #14

Closed jasonw-rr closed 3 years ago

jasonw-rr commented 3 years ago

Orb version:

0.2.0

What happened:

No actual workflow was triggered

Expected behavior:

We are expecting to see the workflow defined in build.yml running.

Additional Information:

A tag was pushed to our GitHub repo and triggered CircleCI setup workflow. At the end of the setup, we have this step:

- continuation/continue:
       configuration_path: .circleci/build.yml
       parameters: /tmp/pipeline-parameters.json

and the actual runtime output was:

{
  "continuation-key": "*********",
  "configuration": "< the content of our build.yml >",
  "parameters": < the content of our pipeline-parameters.json >
}
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 21892  100    16  100 21876    166   222k --:--:-- --:--:-- --:--:--  222k
{"message":"OK"}
CircleCI received exit code 0
jasonw-rr commented 3 years ago

Turns out this is not a bug, and all the jobs in build.yml must have the same tag filters as stated in the doc. It would be much nicer to have the same "Not run" status on the ignored followup workflow too, like the setup config.yml