control freak: master declined in branch model check

[Sebastian M.]

We are evaluating control freak ATM.

I have configured a standard gitflow branch model in bitbucket 6.1.1 (master, develop, feature/, hotfix/, release/).

Control freak is configured to check new branches to match the branch model.

I created an empty repo, cloned it, initialized gitflow and tried to push master and develop branches.

One push of master (=production) or develop (=development) fails, whatever I push first works second not.

It seems that configured production (master) and development (develop) branches of the branch model are not considered in the check:

pre-receive hook declined Push rejected branch name: "master".

Control Freak

Push rejected branch name: "master". New branches must comply with this repository's branching model. Allowed names: bugfix/, feature/, hotfix/, release/

---

[Julius Davies [bit-booster.com]]

Thanks for this bug report! Confirmed and replicated!

We plan to get a fix out for this promptly.

In the meantime, here's a workaround:

• If the top-level "Enabled For" control is left unchecked for "[ ] Empty Repos", then you can get 'master' pushed up as long as it happens on the very first push (since empty repos will not trigger the control-freak checks in this case).

Nonetheless, I plan to have a fix published in marketplace.atlassian.com within a couple hours.

[Sebastian M.]

Thanks alot for fixing this!

The workaround only works for the first push. As said, when pushing master first, push of develop fails afterwards:

pre-receive hook declined Push rejected branch name: "develop".

Control Freak

Push rejected branch name: "develop". New branches must comply with this repository's branching model. Allowed names: bugfix/, feature/, hotfix/, release/

[Julius Davies [bit-booster.com]]

Sorry this is taking longer to fix than we expected! Getting the current branch model config programmatically for "development" and "production" within a given repo and project is much trickier than I thought it would be.

(Our fix is ready - we're just testing it before publishing it. ETA: 8pm pacific time, March 27th, 2019.)

[Julius Davies [bit-booster.com]]

Look for v2019.03.27 in marketplace.atlassian.com ! (And thanks for the bug report!)