Skip to content

Added NewBranchEligibilityFilter#202

Open
Setre14 wants to merge 1 commit into
mohamicorp:masterfrom
Setre14:omitNewBranchWoithoutChanges
Open

Added NewBranchEligibilityFilter#202
Setre14 wants to merge 1 commit into
mohamicorp:masterfrom
Setre14:omitNewBranchWoithoutChanges

Conversation

@Setre14

@Setre14 Setre14 commented Aug 22, 2017

Copy link
Copy Markdown

Skip new branches without changes which are created in Bitbucket

@bfarka

bfarka commented Aug 24, 2017

Copy link
Copy Markdown

@alexBraidwood it would be great if you find time to have a look on that PR?

we would need it since that would reduce the load of our jenkins a lot...

THX

@alexBraidwood

alexBraidwood commented Sep 1, 2017

Copy link
Copy Markdown
Contributor

@Setre14 First of all, thanks for the pull request.

Is this a fix for Jenkins builds that build for any branch committed to?
If that's the case, this sounds easily fixed by specifying which branches to build in Jenkins instead of eating every commit to every branch.

EDIT: For clarity.

@bfarka

bfarka commented Sep 4, 2017

Copy link
Copy Markdown

@alexBraidwood : me and @Setre14 worked on this PR...

what it does is...

if you create an branch in BB (or via an linked jira) the new branch without any changes gets built on Jenkins..

we want to skip that very first build since the result should be the same like on master and creates a bunch of load on our systems..

@rbrindl

rbrindl commented Jun 11, 2018

Copy link
Copy Markdown

Is there any progress with this PR? We could use it as well. As described above, many of our devs use the workflow "create branch from jira", so all those builds (up to 50 a day) are completely useless and block the CI from doing more useful tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants