Multiple Workflows Alongside "Setup" Workflows
complete
N
Nathaniel Morihara
It would be great if you could have multiple workflows in your CircleCI config.yml alongside a "setup" workflow.
Right now, the "setup" workflow feature requires that you have only a single workflow in your base CircleCI config.yml. However, this makes it impossible to have workflows that are triggered via schedules AND workflows triggered by Github pull requests and API calls.
Salil Subbakrishna
complete
A few months ago we released Scheduled Pipelines (not to be confused with Scheduled Workflows, which is what we have had before). Scheduled Pipelines uses a completely different mechanism for triggering pipelines and is more similar to how we trigger pipelines for pushes/PRs and API calls. This should enable using both a setup workflow and a schedule.
Salil Subbakrishna
I'd like to clarify the issue here. Do you need multiple workflows in the .circleci/config.yml to solve a particular use case? Or is the primary issue that you cannot use schedules with a setup workflow?
N
Nathaniel Morihara
Salil Subbakrishna: Hey, yup I can add more context:
We have multiple workflows in our CircleCI configuration. For simplicity, say we have two workflows:
1) gh-pr-workflow (we want this to be triggered by Github pull requests)
2) cron-workflow (we want this to run once a day at a certain time)
We want 'gh-pr-workflow' to be a "setup" workflow (we don't care if 'cron-workflow' is a "setup" workflow or not). If we turn on setup workflows for the config, then we can no longer have the 'cron-workflow' triggered by a schedule (because we're only allowed a single workflow, so we have to pick one trigger).
The problem is, the requirement that there be a SINGLE workflow in the base .circleci/config.yml means that we have to choose to EITHER a setup workflow that is triggered by Github pull requests OR one that is triggered by a schedule - there isn't the capability to have both triggers.
Does that help?