X Y updated Bug JENKINS-16981
Change By: X Y (27/Feb/13 10:02 AM)
Description: I am using the build-on commit feature with github. 

- I've got a dedicated user that has pull-only to several of my repositories.
- GitHub Web Hook is configured like so:
    + "Let Jenkins auto-manage hook URLs" enabled
    + "Override Hook URL" disabled
    + "GitHub credentials" = credentials of the dedicated user
- In the job configuration, "Build when a change is pushed to GitHub" is enabled
- On github.com in the "Service Hooks" section of my repo, I've added a "WebHook URL": https://XXX/github-webhook/

I've tested the hook (using "Test Hook" button in github Service Hooks configuration) in the following cases and here is what I observe:
- OK (= a build is triggered) if the repo contains a simple maven project at the root of the repository
- OK if the repo contains several (unrelated) maven projects and jenkins job root pom points to one of the projects
- NOT OK if the repo contains a multi-module maven project at the root of the repository and jenkins job root pom points to the 'master' pom, like so:
<repo>/
..pom.xml <- root pom
..module1
/
....src/
....pom.xml
..module2
/
....src/
....pom.xml

thanks


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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to