[JIRA] [git-plugin] (JENKINS-23608) Git plugin doesn't build jobs that use the inverse build strategy for new branches

Wed, 24 Dec 2014 19:41:23 -0800

 
Mark Waite edited a comment on Bug JENKINS-23608

While evaluating the proposed pull request, I was unable to duplicate the problem with git-client-plugin 1.13.0 and git-plugin 2.3.2.

I don't have a way of allowing a GitHub hook into my Jenkins server, so I had to approximate it with the following steps:

  1. Create a git repository on my Ubuntu machine, accessible through git protocol
  2. Add the post-receive hook to that repository with the contents: 
    # /bin/bash
curl -s http://localhost:8080/git/notifyCommit?url=""
curl -s http://localhost:8080/git/notifyCommit?url=""
  3. Submit changes to the master branch and branch1 in that repository as "starter commits"
  4. Configure two Jenkins jobs to use that repository, one with inverse choosing strategy, one with default choosing strategy (poll SCM, no schedule, etc.)
  5. Build both new jobs once
  6. Submit a new change to the "master" branch, confirm the commit hook runs and only the master branch job runs
  7. Submit a new change to the "branch1" branch, confirm the commit hook runs and only the branch1 job runs



If the problem still exists in your case (and isn't visible in mine), then I'll likely just accept the bug fix and rely on you to verify it after the next version of the git-plugin has released.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to