Submit Your Ideas

We want to hear from you - vote for the features and improvements you'd most like to see, or submit your own ideas if you don't find them already listed.

Allow branch whitelist to override “Only build pull requests”

This is mostly copied from a thread in the Community Forum here - https://discuss.circleci.com/t/allow-branch-whitelist-to-override-only-build-pull-requests/6392

The goal is to be able to have Circle automatically build all commits to the default branch *as well as* other specially named branches without having to build non-PR branches. This is very useful for those of us who have expensive steps in our build process (like tests that run on external servers, or those using the mac OS builds who want to save minutes).

Minimum viable here would be to allow a list of branch names. Better would be to allow a list of branch names and/or regexes to specify branches.

 

We have a work-around that we developed locally by opening up fake PRs from our release branches into master as part of our process. But it's manual, error prone, and inelegant. Supporting a whitelist would be much nicer.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Feb 6 2018
  • Future consideration
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    15 Mar 14:57

    I think this is a really common scenario for people with multiple protected branches corresponding to multiple development environments. This really needs to get implemented!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    08 Jun 16:00

    The lack of this feature is a bit of a deal-breaker for anyone wishing to use GitFlow or similar branching semantics.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    19 Jun 15:32

    This is really necessary specially for the ones that use mac OS builds as it has a limit amount of time allowed.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    26 Jul 18:04

    Yes please, echo the sentiments in the comments here.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    01 Aug 21:08

    This is an absolute necessity for our workflow.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    17 Aug 11:51

    This is a necessity

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    05 Sep 11:28

    This is also crucial for some of our core pull request features

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    07 Nov 09:04

    We require this functionality as well. Ideally it would be behind a regex.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    09 Nov 20:17

    This is very much needed, the setting is like a sledgehammer when you need a scalpel as it is today.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    12 Nov 18:05

    This is absolutely necessary feature. As we want PR to build and run tests before merge. But we want the artefacts to be stored for the specific branch on a bucket.