[Product Update] Multiple configuration files per project

Build Environment
1

How to

  1. Go to Project Settings in the CircleCI UI. Click the “Pipelines” tab

  2. Create and save a pipeline where we will pull your CircleCI configuration from. You can use a file that is not named .circleci/config.yml.

  3. Click on the “Triggers” tab. Click “Add Trigger”.

  4. Create a trigger and select the pipeline that you created in step 2 above. Save the trigger.

Now every time you push to the repository that you selected, you should see a pipeline trigger using the new pipeline as well. Read more in our docs.

2

WARNING: We are currently working through a bug that affects this experience.

If multiple triggers exist that use different Configuration Sources, all triggers currently incorrectly use the same Configuration Source.

Will post an update on here as soon as this is resolved.

3

I can confirm that this is fixed when using different YML files within the same repository as configuration sources.

When using configuration files from external repositories, we are still experiencing some issues.

4

The bug that @Benny mentioned above has now been fixed: Unlocking any cross-repo pipeline and trigger setups, including central config management - CircleCI

1 Like
5

Hey Benny
Seems like we still have an Issue with this, as we have multiple config files in one repo and when we are trying to trigger the pipeline using different pipeline configured to use different config sources still we do see same set of prefilled parameters

6

Can you send us an email to sebastian@circleci.com & benedetta@circleci.com with a link to your CircleCI project please? We can debug there

7

@mankarandhamija
I reached out by email too, but wanted to let you know that the bug you raised is fixed, so now the parameters in the “Trigger pipeline” modal are auto-populated based on the pipeline you select - as long as it’s a pipeline integrated through the CircleCI GitHub App integration. We expect to be able to fix this behaviour for pipelines integrated via the OAuth integration too within the next few weeks.