You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
Hello, we are attempting to us conditional workflows and pipeline parameters so that we can easily deploy our website. So we have two workflows: 1) a full build and 2) just deploy the site.
Problem steps:
Merge a change to to origin/production, which triggers a full build (default pipeline parameters)
Soon after, make a change to the blog which uses the circleci API to trigger a pipeline build (i.e. parameters: { "build": false, "deploy-site": true })
Observe on the circleci site that the first build has been canceled.
Since the selected workflows aren't the same, I don't think these builds should be considered "redundant".
The text was updated successfully, but these errors were encountered:
johnjensenish
changed the title
"Auto-cancel redundant builds" should be away of conditional workflows
"Auto-cancel redundant builds" should be smarter about conditional workflows
Jul 27, 2019
Hello, we are attempting to us conditional workflows and pipeline parameters so that we can easily deploy our website. So we have two workflows: 1) a full build and 2) just deploy the site.
Problem steps:
origin/production
, which triggers a full build (default pipeline parameters)parameters: { "build": false, "deploy-site": true }
)Since the selected workflows aren't the same, I don't think these builds should be considered "redundant".
The text was updated successfully, but these errors were encountered: