Blacklist priority not working as expected for feature branches

[mikeycmccarthy]

Hi, I think that either the blacklist/whitelist has a bug, or the documentation is incorrect/misleading.

The documentation states 'The blacklist takes precedence over whitelist. I.e. a branch will not be built if the blacklist pattern matches to the branch name'.

On our setup we have 'master' as the blacklist pattern, and * as the whitelist pattern, which I assume to mean build any branches EXCEPT master.

I can clearly see that master branch is being built:

09:07:01.778 [go] setting environment variable 'GO_SCM_XXX_LABEL' to value '8f429c4a5517b462bf973b1a947697a15e2f35b8' 09:07:01.778 [go] setting environment variable 'GO_SCM_XXX_URL' to value '[email protected]' 09:07:01.778 [go] setting environment variable 'GO_SCM_XXX_BRANCHBLACKLIST' to value 'master' 09:07:01.778 [go] setting environment variable 'GO_SCM_XXX_BRANCHWHITELIST' to value '*' 09:07:01.778 [go] setting environment variable 'GO_SCM_XXX_CURRENT_BRANCH' to value 'master'

Is this my misunderstanding of the plugin?

Thanks

[ashwanthkumar]

@mikeycmccarthy Can you please help me understand if the logs you saw were from the first time build or master is getting built on every push ?

[mikeycmccarthy]

Let me check and confirm, thanks

[digitalcherry]

I can confirm that I am also having the same issue, I have a blacklist of "master,develop" and a whitelist of * but the build keeps pulling master.

[dokaspar]

Same issue here. I simply added "master" into the blacklist and my pipeline never triggers anymore, no matter on which branch commits are pushed.