[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials

Thu, 13 Mar 2014 06:25:24 -0700

Our repository structure in the SVN looks like this:

IAB2.5
  +-- trunk
  |     +-- Library
  |           +-- FolderA
  |           |     +-- externalA.c
  |           +-- FolderB
  |           |     +-- externalB.c
  |           +-- externalC.c
  |
  +-- branches
  |     +-- ProjectA
  |     |     +-- FolderA
  |     |     |     +-- external1.c
  |    	|     +-- FolderB
  |    	|     |     +-- external2.c
  |    ...    +-- external3.c
  |
  +-- Projects
        +-- ProjectB       <--- Jenkins Job A - watched for svn changes
        |     +-- FolderA  <--- SVN External (^/trunk/Library)
        |     +-- FolderB  <--- SVN External (^/branches/ProjectA)
        |     +-- FolderC
        |           +-- internal.c
        |
        +-- ProjectB1      <--- Jenkins Job B - triggered by Job A
        |     +-- FolderA  <--- SVN External (^/trunk/Library)
        |     +-- FolderB  <--- SVN External (^/branches/ProjectA1)
        |     +-- FolderC
       ...          +-- internal.c

Job A in Jenkins triggers on all SVN changes in the root Project, e.g.

  • externalA.c
  • externalB.c
  • external2.c
  • external3.c
  • internal.c



--> they all trigger the checkout and rebuild of our ProjectB.

So a change in your external.c should be able to trigger your Job B too, as there is a new revision number created for it on the commit.



Also our ProjectB1 gets built by Job B which is started by Job A after it has finished.

They all work well now (all Jobs with additional credentials set, though).



Anyway, instead of post-commit hook trigger or any other hook we use svn polling (check repository every 1/4 hour). Could this be the reason why our setup works?
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