Custom Pipelines not triggering

[doughlass]

Not sure if this is by intention or a bug.

When making use of custom pipelines like this image.

I have CircleCI configs that live in a different repository to the actual code eg: circleci-central and client-repo

If I try to trigger the pipeline and the parameters all match up etc then it will likely use the config from the centralised repo.

But if the commit that was deployed last contains “[skip ci]” then the custom pipeline won’t trigger, even if you’re trying to manually trigger it.

We won’t be using client-repo/.circleci/config.yml for this project so it’s trigger was removed, so I’m unsure how exactly I’m able to trigger a custom pipeline with parameters when the last commit was ci skipped.

[Benny]

Hi @doughlass , this looks like a bug on our side, thanks for reporting it.
I will bring it up with the team.
I’m assuming you are not currently completely blocked by this, right?

[doughlass]

I’d consider it a major blocker in general.

as I’ve transitioned our clients projects to use custom pipelines, if for example someone commits with skip ci, we aren’t able to manually trigger successfully.

this has been an issue for quite some time.

the only way to bypass is by sending an empty commit, which also triggers a stage deployment and we need to cancel.

only after an empty commit is sent are we able to run a manual trigger either with the trigger button or api.