Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-22280

Browser support for multiple subversion repositories

    • Icon: New Feature New Feature
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • Jenkins 1.552/Subversion plugin 2.2

      We use separate svn repositories as "common" repos are shared across products.
      In looking at the changelog.xml file, it appears that the repo url isn't captured as part of the change information.

      Having an entry for only 1 browser url is like having a broken watch that's only right twice a day.
      As long as the file you're looking at is in the configured url, it works.

      If there's a workaround for this I'd love to hear it.

          [JENKINS-22280] Browser support for multiple subversion repositories

          John David added a comment -

          Actually, this should probably be a bug.
          If someone clicks on a browser link for a revision that exists in the configured repository, they are (incorrectly) shown that changeset.

          Since the repo isn't captured in changelog.xml, it's impossible to "know" what repository the change came from.

          So...
          If multiple repositories are configured
          a) Remove the browser from the config and the browser link in the "Changes" section.
          b) Set the browser to "None" and if None is set, don't show the browser link in Changes.
          c) Fix the problem so the browser can deal with more than one repository.

          I'm kind of partial to the third option.

          John David added a comment - Actually, this should probably be a bug. If someone clicks on a browser link for a revision that exists in the configured repository, they are (incorrectly) shown that changeset. Since the repo isn't captured in changelog.xml, it's impossible to "know" what repository the change came from. So... If multiple repositories are configured a) Remove the browser from the config and the browser link in the "Changes" section. b) Set the browser to "None" and if None is set, don't show the browser link in Changes. c) Fix the problem so the browser can deal with more than one repository. I'm kind of partial to the third option.

          Daniel Beck added a comment -

          This duplicates JENKINS-7647.

          anstaafl: The existing data (changelogset + recorded repos/revisions on the build) can be used to infer the correct repository almost always. See my unreleased TortoiseSVN Browser Plugin.

          Daniel Beck added a comment - This duplicates JENKINS-7647 . anstaafl : The existing data (changelogset + recorded repos/revisions on the build) can be used to infer the correct repository almost always. See my unreleased TortoiseSVN Browser Plugin .

            Unassigned Unassigned
            anstaafl John David
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: