Infrastructure
  1. Infrastructure
  2. INFRA-5844

subversion commits are missing in OpenJPA JIRAs

    Details

      Description

      I recently noticed that our (OpenJPA) subversion commits are not getting logged to our JIRAs. Use OpenJPA-2326 as an example. You'll noticed it logged a commit done by me on Jan 22, 2013. But, we have had several commits since that day with the same "OPENJPA-2326" tag line and they are not showing up in the JIRA. Did something change recently that is preventing these commits from getting logged?

      Thanks,
      Kevin

        Activity

        Hide
        #asfinfra IRC Bot added a comment -
        <danielsh> No, it's been this way for months, known issue
        Show
        #asfinfra IRC Bot added a comment - <danielsh> No, it's been this way for months, known issue
        Hide
        Kevin Sutter added a comment -
        I'm sorry, but can I get a bit more information? It hasn't been this way for months, since a commit I did just over 2 weeks ago (Jan 22) was logged to the associated JIRA. Is there another JIRA to reference to track this issue? Is it ever going to be resolved? Is this an SVN issue? JIRA issue? Apache configuration issue? Just attempting to figure out if this is a change in the processing, or if it will eventually start working again.

        Thanks for your help!
        Kevin
        Show
        Kevin Sutter added a comment - I'm sorry, but can I get a bit more information? It hasn't been this way for months, since a commit I did just over 2 weeks ago (Jan 22) was logged to the associated JIRA. Is there another JIRA to reference to track this issue? Is it ever going to be resolved? Is this an SVN issue? JIRA issue? Apache configuration issue? Just attempting to figure out if this is a change in the processing, or if it will eventually start working again. Thanks for your help! Kevin
        Hide
        Daniel Gruno added a comment -
        Hi Kevin,
        It's a JIRA issue, as svn and git did not want to play nice with JIRA, and it has been like this for quite a while.
        You seem to have been using some fisheye thingy for your integration, which is not something in my command to restore.
        What we can do instead is add you to our svn/git2jira implementation, which will attach comments to issues as svn or git commits that refer to a ticket are made.
        It's slightly different from what you've been used to, in that this feature appears as a comment instead of in the source tab, but if you can work with that, we can have you set up within a few moments. The information logged is roughly the same (svn link, who did the commit and the commit log)
        For an example of what this looks like, take a look at https://issues.apache.org/jira/browse/COUCHDB-1313 (that's from git, but you get the gist)
        Show
        Daniel Gruno added a comment - Hi Kevin, It's a JIRA issue, as svn and git did not want to play nice with JIRA, and it has been like this for quite a while. You seem to have been using some fisheye thingy for your integration, which is not something in my command to restore. What we can do instead is add you to our svn/git2jira implementation, which will attach comments to issues as svn or git commits that refer to a ticket are made. It's slightly different from what you've been used to, in that this feature appears as a comment instead of in the source tab, but if you can work with that, we can have you set up within a few moments. The information logged is roughly the same (svn link, who did the commit and the commit log) For an example of what this looks like, take a look at https://issues.apache.org/jira/browse/COUCHDB-1313 (that's from git, but you get the gist)
        Hide
        Kevin Sutter added a comment -
        Hi Daniel,
        Thanks for the information. The fisheye thingy is just a viewing server for the changes. It's an atlassian server for various open-source projects. We recently had to resolve this server as well (https://support.atlassian.com/browse/FSH-10783). In that case, the commit messages were still getting logged to the JIRAs, but the links were not working due to the fisheye server not being available...

        All I really care about is to get some type of link between our commits and the associated JIRAs -- comment tab, source tab, it doesn't matter. If you get our project added to your tooling, that would be great.

        So, when you say "our implementation", who is this? Are you referring to CouchDB, or some other project? Just wondering who to "thank". :-)

        Thanks,
        Kevin
        Show
        Kevin Sutter added a comment - Hi Daniel, Thanks for the information. The fisheye thingy is just a viewing server for the changes. It's an atlassian server for various open-source projects. We recently had to resolve this server as well ( https://support.atlassian.com/browse/FSH-10783 ). In that case, the commit messages were still getting logged to the JIRAs, but the links were not working due to the fisheye server not being available... All I really care about is to get some type of link between our commits and the associated JIRAs -- comment tab, source tab, it doesn't matter. If you get our project added to your tooling, that would be great. So, when you say "our implementation", who is this? Are you referring to CouchDB, or some other project? Just wondering who to "thank". :-) Thanks, Kevin
        Hide
        Daniel Gruno added a comment -
        Ours in this case means a homebrewed ASF implementation.
        I've set up the configuration to link any new commits to their respective JIRA tickets.
        Enjoy, and should it not work or if you have any questions, feel free to reopen the issue.
        Show
        Daniel Gruno added a comment - Ours in this case means a homebrewed ASF implementation. I've set up the configuration to link any new commits to their respective JIRA tickets. Enjoy, and should it not work or if you have any questions, feel free to reopen the issue.

          People

          • Assignee:
            Daniel Gruno
            Reporter:
            Kevin Sutter
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development