[ 
https://issues.jenkins-ci.org/browse/JENKINS-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163538#comment-163538
 ] 

Klaus Azesberger edited comment on JENKINS-6450 at 6/6/12 9:14 AM:
-------------------------------------------------------------------

we too have a similar (probably the same) issue, using a customized 
subversion-plugin based on 1.41-snapshot (fixed 2 issues with variables like 
$MY_PROJECT_SVN_URL in scm-url of projects) with jenkins 1.465

we dont use post-commit-hook, we use simple scm-polling as build trigger.

the svn polling protocol says "no changes", but when i manually trigger the 
build it updates changes "behind an svn external" correctly.
                
      was (Author: mcklaus):
    we too have this issue, using a customized subversion-plugin based on 
1.41-snapshot (fixed 2 issues with variables like $MY_PROJECT_SVN_URL in 
scm-url of projects) with jenkins 1.465
                  
> post-commit hook does no handle svn:externals
> ---------------------------------------------
>
>                 Key: JENKINS-6450
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-6450
>             Project: Jenkins
>          Issue Type: Bug
>          Components: subversion
>    Affects Versions: current
>         Environment: Windows, Hudson V1.356, Subversion Plug-in V1.17, "Poll 
> SCM" enabled and left empty 
>            Reporter: Axel Heider
>
> I've set up a post-commit hook that send a post request with the changed 
> files (http://%HUDSON%/hudson/subversion/%UUID%/notifyCommit?rev=%REV%). It 
> works fine except for changes in directories or files referenced via 
> svn:externals. If something changes there, the project is no rebuild. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to