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

[chiki...@java.net (JIRA)]

chikigai commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Daniel Beck OK, here's some more info which hopefully would be of some use. Let me explain with some additions to the repository structure I used previously: RepoA ├── ProjectA │ └── trunk │ ├── FolderA │ └── FolderB │ └── external.c └── ProjectB └── trunk ├── FolderA │ └── internal.c └── FolderB <--- SVN External (^/ProjectA/trunk/FolderB) I have two jobs where: [Job A] Checks out ProjectA/trunk and then triggers Job B. (I created this job since changes in "external.c" would not be picked and trigger Job B) [Job B] Checks out ProjectB/trunk and runs a build. Contains an additional credential as discussed in earlier comments. And now a list of build triggers I tried with results: [Job A + Manual trigger] Job A succeeds, Job B is triggered and succeeds. [Job B + Manual trigger] Job B succeeds. [Change/Commit "internal.c" + post-commit hook trigger] Job B succeeds. [Change/Commit "external.c" + post-commit hook trigger] Job A succeeds, Job B is triggered and fails with authentication failure on the SVN external. This failure occurs every single time via a post-commit hook trigger when "external.c" is commited. Stack trace is exactly the same as posted in comment-196434.

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.