Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Not Kicked off on Branch Creations #20

Closed
bassrock opened this issue Oct 13, 2014 · 5 comments
Closed

Build Not Kicked off on Branch Creations #20

bassrock opened this issue Oct 13, 2014 · 5 comments

Comments

@bassrock
Copy link
Contributor

Builds are not getting kicked off for me on branch creations. Is this just me? Subsequent pushes work but not pushes on creation.

@marciobueno1
Copy link

I am experiencing the same problem, but in my case subsequent pushes are not working.
After the push of a new branch, I need to go to Jenkins and add the new branch on the project settings (Filter Branches section), and only then, subsequent pushes work.

@jchristi
Copy link

I am experiencing similar issues though I can't identify exactly how consistent it is. Subsequent pushes never seem to work and initial pushes work "some of the time".

@xaniasd
Copy link
Contributor

xaniasd commented Oct 25, 2014

By default, the filter is bypassed (meaning that all branches are automatically white-listed). If the user selects some branches (in the Filter Branches section), then the filter will be applied. New branches are then by default excluded from the white-list and thus filtered out. This explains the behavior in the case of @marciobueno1

Concerning the original problem, GitLab apparently does not see pushing new branches as a normal Push Event so it doesn't trigger the job as it should (I see a trigger with an empty JSON payload).

@marciobueno1
Copy link

@xaniasd, in my case I didn't select any branches. But, when I clicked Configure again, then all the braches from the repository were selected. Maybe, it should have a checkbox to activate the filter, or could have an option like "All Branches" in the Combo Box to avoid this problem.

@bassrock
Copy link
Contributor Author

@marciobueno1 please create a separate issue for that.

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

No branches or pull requests

4 participants