Branch filtering is not working properly


I have a .circleci/config.yml file with some jobs ignoring some specific branches:

Notice how I’m ignoring branches called l10n_. These branches are ignored because they are created automatically by Crowdin, which sends a new commit for each change in any language and that pollutes our CI. Note that the jobs being ignored are the first ones of the workflow, so if those don’t get executed the rest of the workflow isn’t going to be either.

But I have a lot of builds from PR, which merges commits from a branch called l10n_0.11-stable into 0.11-stable. I’ve checked it and the PR is up to date with the base branch, so it has the config where the branch should be ignored.

I’ve tried ignoring branches by full name, (eg l10n_0.11-stable, without wildcards), and that works as expected, but when I use a wildcard it stops working.

Maybe it’s because I’m using dots and dashes in my branch name and the wildcard fails to find it? Or am I missing something else?

Can someone help me here please?


Branch filtering ignore

Update: on a branch called l10n_master, the wildcard isn’t working either, so I’m having the workflows being scheduled :confused:


Also note that this is due to not having the autocancel for workflows, which has been asked for a long time now :disappointed:


Try changing the filter from l10n_* to /^l10n_*/ and making sure this is in the default branch and parent branch of those autogenerated PRs.


Argh, of course!

Thank you very much!


To mark things as solved in Discourse, you don’t need to edit the title - there’s a proper acceptance system. See the toolbar under Feliciano’s answer? Next to the “like” and “link” buttons there is a “solved” button - tick that and the system will properly mark the thread as solved.


@halfer thanks! I’ll do that!

@FelicianoTech I’m checking it and it doesn’t seem to be working actually :confused:

See this PR: if you open any commit from it, and browse the files, and visit the CircleCI config file, I’m using /^l10n_*/ as suggested previously, but I still see builds for those commits. Eg the first commit of that PR is fdb9dbc:

The config file for that commit:

The build in CircleCI:

Any idea of what might be happening here?



I believe you can’t use a YAML list when trying to use regex. So for example, instead of doing this:

- build_design_app:
          - /^l10n_*/


- build_design_app:
        ignore: /^l10n_*/


@FelicianoTech I’ll try it, but in this example you show how to use a regexp both as part of a list and as a single value:


True. Let me know if that works, I would like to clarify how this is suppose to work and/or if there’s a bug we’re not aware of.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.