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

Support Bugtraq properties for Subversion changelogs

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Platform: All, OS: All

      The Bugtraq specification defines properties for Subversion repositories to
      allow client software to link commit messages to issue reports in a web-based
      issue-tracking system.

      See http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc/issuetrackers.txt
      (username 'guest', no password).

      Hudson could detect these properites in a Subversion working copy and use them
      to find issue numbers in log messages so that appropriate hyper-links can be
      inserted in the changes pages.

          [JENKINS-1060] Support Bugtraq properties for Subversion changelogs

          dwdyer added a comment -

          The only thing that is stopping me from implementing this at the moment is that
          it could interfere with the existing ChangeLogAnnotators in the Jira and Trac
          plug-ins.

          I think that the Bugtraq approach is a more general solution to the same
          problem that these annotators address. It does require the properties to be
          present in the repository, but it provides configuration for all tools that use
          the Subversion repository, not just Hudson, and it doesn't require Hudson to
          know about every possible issue tracker.

          I'm open to suggestions on the best way to implement this without causing
          problems for the existing annotators.

          dwdyer added a comment - The only thing that is stopping me from implementing this at the moment is that it could interfere with the existing ChangeLogAnnotators in the Jira and Trac plug-ins. I think that the Bugtraq approach is a more general solution to the same problem that these annotators address. It does require the properties to be present in the repository, but it provides configuration for all tools that use the Subversion repository, not just Hudson, and it doesn't require Hudson to know about every possible issue tracker. I'm open to suggestions on the best way to implement this without causing problems for the existing annotators.

          Mark Lewis added a comment -

          If the bugtraq support is both optional and extensible...

          1. Implementing it wouldn't affect current deployments unless someone manually enables it at the same time as these other (currently incompatible) plugins. OTOH, for those who don't have any issue tracker plugins installed, this would instantly provide a useful feature.
          2. Existing issue tracker plugins could eventually replace or supplement their own support with official bugtraq support.
            • It would be up to each plugin, but my suggestion would be to give users two choices for configuring their issue tracker plugins:
              • Manually through Hudson, as it is done now.
              • Automatically/dynamically through bugtraq properties.
            • May want to get some input from the maintainers of those plugins about how to go about this. This could mean that for their other features to work, the plugins would require a lot more per-project settings since bugtraq properties are defined at the repository level.
          3. This would still allow issue tracker plugins to add popular features such as:
            • Tooltips of each issue's description for the links in Hudson.
            • Integration notification through the tracker (ie. adding comments).

          Mark Lewis added a comment - If the bugtraq support is both optional and extensible... Implementing it wouldn't affect current deployments unless someone manually enables it at the same time as these other (currently incompatible) plugins. OTOH, for those who don't have any issue tracker plugins installed, this would instantly provide a useful feature. Existing issue tracker plugins could eventually replace or supplement their own support with official bugtraq support. It would be up to each plugin, but my suggestion would be to give users two choices for configuring their issue tracker plugins: Manually through Hudson, as it is done now. Automatically/dynamically through bugtraq properties. May want to get some input from the maintainers of those plugins about how to go about this. This could mean that for their other features to work, the plugins would require a lot more per-project settings since bugtraq properties are defined at the repository level. This would still allow issue tracker plugins to add popular features such as: Tooltips of each issue's description for the links in Hudson. Integration notification through the tracker (ie. adding comments).

            dwdyer dwdyer
            dwdyer dwdyer
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: