Re: Git plugin - feature branch frustrations

2015-08-04 Thread nicolas de loof
ls-remote is indeed sufficient to retrieve branches HEADs, and we got such a change implemented in 2.4.0 development build, BUT git plugin do have some legacy logic to only consider tip branches, i.e. exclude branches that are ancestors for other branches. As a result, we ended with infinite build

Re: Git plugin - feature branch frustrations

2015-08-03 Thread Mark Waite
I agree, it is poor user experience to require a workspace if one is not really needed. Will you be investigating further and submitting one or more bug reports describing the problems you've found? Will you be submitting pull requests (with tests) which show the problems and then show that your

Re: Git plugin - feature branch frustrations

2015-08-03 Thread Nigel Magnay
I don't see why polling via a workspace should be required. 'git ls-remote' is sufficient to determine branch names and SHA1s, and thus to determine if there are any changes to build. And in any case, there will be no workspace, since all builds on lightweight docker containers, torn down immediate

Re: Git plugin - feature branch frustrations

2015-08-03 Thread Mark Waite
Considering how poorly a number of developers think of the maven project type, aren't you at least tempted to try a multi-branch with a maven build step, rather than using the maven project type? I think your users will thank you. Mark Waite On Mon, Aug 3, 2015 at 10:30 AM Nigel Magnay wrote:

Re: Git plugin - feature branch frustrations

2015-08-03 Thread Nigel Magnay
Multi-branch looks useful, but sadly this project uses the maven project type. I did see some reports about it getting confused that the branch name has a '/' in it. If I get a chance I'll try and diagnose. On Mon, Aug 3, 2015 at 5:20 PM, Mark Waite wrote: > I've recently been using the multi-

Re: Git plugin - feature branch frustrations

2015-08-03 Thread Mark Waite
I've recently been using the multi-branch plugin with great success. It automatically creates a new job for each branch it detects, rather than "hiding" the detection of a new branch inside the execution history of a single job. You might experiment with it to see if it meets your needs better th

Git plugin - feature branch frustrations

2015-08-03 Thread Nigel Magnay
So I'm trying to set up the git plugin to build feature branches. Features are on branches like feature/foo and feature/blah. This is a common pattern as it's derived from git-flow. I seem to have tried every combination of branch specifiers, and all this results in is jenkins building the same S