[JIRA] [subversion] (JENKINS-22778) Changelog entries for externals have become useless

[dan...@beckweb.net (JIRA)]

Daniel Beck created JENKINS-22778 Changelog entries for externals have become useless Issue Type: Bug Assignee: Unassigned Components: subversion Created: 26/Apr/14 10:34 PM Description: This commit broke changelog entries from external locations. Even with the proposed solution to JENKINS-22199 the paths remain broken (presumably except for the JENKINS-18574 use case). From the linked commit's discussion (see full discussion for context): But that's still not the actual problem! Since /trunk/baz/baz doesn't exist anywhere except for a local working copy, it will break all repo browsers even when implemented "correctly": .../repo2/trunk/baz/ simply does not exist as an actual path. And even if there is a repo browser that supports "virtual" paths for browsing, it won't be able to show the diff between two revisions of a completely different repository: Given the revisions in my test setup above, it's likely to result in links to something like http://svnbrowser/repo2/trunk/baz/baz?rev=4, when that revision doesn't even exist in that repo. I also tested the "exclude paths" option: While the changelog now shows the changed path baz/baz, I have to exclude the location /projectX/trunk/.* to ignore it. Which is obviously really confusing: how do you get from an accidentally polling-triggered build's change log to the correct location to exclude in the configuration? It's trivial in the old format, you just copy and paste from the change log. And while we're at it, changelog.xml lost the information about what kind of entity this is (tested with the master snapshot build): <path action="" class="code-quote">"M" kind="unknown">baz/baz</path> as opposed to: <path action="" class="code-quote">"M" kind="file">/projectX/trunk/baz</path> Environment: Subversion Plugin 2.0+ Project: Jenkins Priority: Critical Reporter: Daniel Beck

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.