Subversion and JIRA integration

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Subversion and JIRA integration

Ragu Nathan

Hi,

I would like to know the Subversion can be integrate with JIRA bug tracking tool.
Ex: I found an  issue in software coding and create a problem report to address root cause, analysis, documents updates , etc and I will use the JIRA to track all above, but Subversion is a configuration management tool to store data ( source code, documents, etc).
Questions:
1. If I use the JIRA tool to address an issue , address all sort of analysis, proposed solutions, implementation details and I want to update the documents or source code in Subversion, is there any way to get into Subversion from JIRA? Not hyperlink. Real integrate environment. In this case I can check if any updates were made in to the documents or source code , which problem reporting # was used to fix the issue.
2. Are both tools integrate together?
3. If so, how much would it cost for floating licence?


Thanks
Ragu.P

Reply | Threaded
Open this post in threaded view
|

Re: Subversion and JIRA integration

Eric Johnson-35
Hi Ragu,

Your question is sort of a tricky one. Well, at least parts of it are. But here's an attempt at an answer.

On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan <[hidden email]> wrote:

Hi,

I would like to know the Subversion can be integrate with JIRA bug tracking tool.

Yes, but it depends on your requirements, and how many development resources you're willing to throw at it, if a commercial vendor doesn't provide it already.
 
Ex: I found an  issue in software coding and create a problem report to address root cause, analysis, documents updates , etc and I will use the JIRA to track all above, but Subversion is a configuration management tool to store data ( source code, documents, etc).

Subversion is a version control tool, not a configuration management tool. While it may certainly be possible to use Subversion in the manner implied, the definition of "configuration management" may lead to requirements that Subversion is less than ideal for.
 
Questions:
1. If I use the JIRA tool to address an issue , address all sort of analysis, proposed solutions, implementation details and I want to update the documents or source code in Subversion, is there any way to get into Subversion from JIRA? Not hyperlink. Real integrate environment. In this case I can check if any updates were made in to the documents or source code , which problem reporting # was used to fix the issue.

As I understand it, JIRA includes an extension API. It certainly should be possible to extend JIRA to get more detailed information about links into Subversion, without, as you indicate "hyperlinking".

There exist integrations into JIRA already for tighter coupling with Subversion, so you could start with those, to see if any of those meet your requirements.
 
2. Are both tools integrate together?

It is left to one's imagination. Both have APIs, so it is possible to add tighter integration to both. For details of how to integrate from Subversion's perspective, check out the "hook" documentation:


Atlassian definitely offers APIs from the JIRA side: https://developer.atlassian.com/server/framework/atlassian-sdk/
 
3. If so, how much would it cost for floating licence?

This mailing list isn't going to be a good source of information about that. And that assumes that you can find an existing commercial vendor of extension(s) that meet your needs.

Eric.

 


Thanks
Ragu.P

Reply | Threaded
Open this post in threaded view
|

Re: Subversion and JIRA integration

Dane Kantner
The actual Atlassian product you're looking for is called FishEye. It works with all major repos including SVN, Git, etc., and its primary purpose is exactly what you're wanting. This is a different license, and runs as a different service than Jira -- which could potentially actually make it cheaper in theory than if it were an actual straight up Jira add-on only since you can license it to a subset of your overall Jira users whom may actually need it.

FishEye is specifically meant for the purpose of integrating source control repositories into Jira. When you check an item in to SVN, as part of the checkin you would provide the Jira ticket # in the log, and then Fisheye indexes that, and then in turn Jira provides links/revision #s/etc. within the Jira ticket. If you then click that it will open in the FishEye interface and you can dive down further into what was checked, see the diff, etc., full source control, etc., in the Fisheye web interface.   Another Atlassian product, Crucible, ties-in to that then to allow you to do a standard code review workflow if you wish, but that is another addon beyond Fisheye even.

Anecdotal notes on this product are it works great but you should really make a good attempt at installing this on the same actual server your SVN server runs on, so you can access the repos by their file:// location -- the difference is 100x speed vs over the network w/ http/svn protocols, and may even be the difference between the product working and being able to index your repo or not. If you don't want to run it on your primary SVN, consider an active mirror sync to the box that fisheye then runs on and index that version locally.

-Dane

On Mon, Sep 30, 2019 at 1:35 PM Eric Johnson <[hidden email]> wrote:
Hi Ragu,

Your question is sort of a tricky one. Well, at least parts of it are. But here's an attempt at an answer.

On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan <[hidden email]> wrote:

Hi,

I would like to know the Subversion can be integrate with JIRA bug tracking tool.

Yes, but it depends on your requirements, and how many development resources you're willing to throw at it, if a commercial vendor doesn't provide it already.
 
Ex: I found an  issue in software coding and create a problem report to address root cause, analysis, documents updates , etc and I will use the JIRA to track all above, but Subversion is a configuration management tool to store data ( source code, documents, etc).

Subversion is a version control tool, not a configuration management tool. While it may certainly be possible to use Subversion in the manner implied, the definition of "configuration management" may lead to requirements that Subversion is less than ideal for.
 
Questions:
1. If I use the JIRA tool to address an issue , address all sort of analysis, proposed solutions, implementation details and I want to update the documents or source code in Subversion, is there any way to get into Subversion from JIRA? Not hyperlink. Real integrate environment. In this case I can check if any updates were made in to the documents or source code , which problem reporting # was used to fix the issue.

As I understand it, JIRA includes an extension API. It certainly should be possible to extend JIRA to get more detailed information about links into Subversion, without, as you indicate "hyperlinking".

There exist integrations into JIRA already for tighter coupling with Subversion, so you could start with those, to see if any of those meet your requirements.
 
2. Are both tools integrate together?

It is left to one's imagination. Both have APIs, so it is possible to add tighter integration to both. For details of how to integrate from Subversion's perspective, check out the "hook" documentation:


Atlassian definitely offers APIs from the JIRA side: https://developer.atlassian.com/server/framework/atlassian-sdk/
 
3. If so, how much would it cost for floating licence?

This mailing list isn't going to be a good source of information about that. And that assumes that you can find an existing commercial vendor of extension(s) that meet your needs.

Eric.

 


Thanks
Ragu.P

Reply | Threaded
Open this post in threaded view
|

Re: Subversion and JIRA integration

Ragu Nathan
Thanks for your responses Eric and Dan,

So FishEye interfaces with JIRA and Subversion.
Do you have the trail versions of these tools ? I could try and see how it works or you have some sort of online demo for me to see how it works.

Your response is appreciated. 

Thanks 
Ragu.P

Sent from my iPhone

On Sep 30, 2019, at 5:06 PM, Dane Kantner <[hidden email]> wrote:

The actual Atlassian product you're looking for is called FishEye. It works with all major repos including SVN, Git, etc., and its primary purpose is exactly what you're wanting. This is a different license, and runs as a different service than Jira -- which could potentially actually make it cheaper in theory than if it were an actual straight up Jira add-on only since you can license it to a subset of your overall Jira users whom may actually need it.

FishEye is specifically meant for the purpose of integrating source control repositories into Jira. When you check an item in to SVN, as part of the checkin you would provide the Jira ticket # in the log, and then Fisheye indexes that, and then in turn Jira provides links/revision #s/etc. within the Jira ticket. If you then click that it will open in the FishEye interface and you can dive down further into what was checked, see the diff, etc., full source control, etc., in the Fisheye web interface.   Another Atlassian product, Crucible, ties-in to that then to allow you to do a standard code review workflow if you wish, but that is another addon beyond Fisheye even.

Anecdotal notes on this product are it works great but you should really make a good attempt at installing this on the same actual server your SVN server runs on, so you can access the repos by their file:// location -- the difference is 100x speed vs over the network w/ http/svn protocols, and may even be the difference between the product working and being able to index your repo or not. If you don't want to run it on your primary SVN, consider an active mirror sync to the box that fisheye then runs on and index that version locally.

-Dane

On Mon, Sep 30, 2019 at 1:35 PM Eric Johnson <[hidden email]> wrote:
Hi Ragu,

Your question is sort of a tricky one. Well, at least parts of it are. But here's an attempt at an answer.

On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan <[hidden email]> wrote:

Hi,

I would like to know the Subversion can be integrate with JIRA bug tracking tool.

Yes, but it depends on your requirements, and how many development resources you're willing to throw at it, if a commercial vendor doesn't provide it already.
 
Ex: I found an  issue in software coding and create a problem report to address root cause, analysis, documents updates , etc and I will use the JIRA to track all above, but Subversion is a configuration management tool to store data ( source code, documents, etc).

Subversion is a version control tool, not a configuration management tool. While it may certainly be possible to use Subversion in the manner implied, the definition of "configuration management" may lead to requirements that Subversion is less than ideal for.
 
Questions:
1. If I use the JIRA tool to address an issue , address all sort of analysis, proposed solutions, implementation details and I want to update the documents or source code in Subversion, is there any way to get into Subversion from JIRA? Not hyperlink. Real integrate environment. In this case I can check if any updates were made in to the documents or source code , which problem reporting # was used to fix the issue.

As I understand it, JIRA includes an extension API. It certainly should be possible to extend JIRA to get more detailed information about links into Subversion, without, as you indicate "hyperlinking".

There exist integrations into JIRA already for tighter coupling with Subversion, so you could start with those, to see if any of those meet your requirements.
 
2. Are both tools integrate together?

It is left to one's imagination. Both have APIs, so it is possible to add tighter integration to both. For details of how to integrate from Subversion's perspective, check out the "hook" documentation:


Atlassian definitely offers APIs from the JIRA side: https://developer.atlassian.com/server/framework/atlassian-sdk/
 
3. If so, how much would it cost for floating licence?

This mailing list isn't going to be a good source of information about that. And that assumes that you can find an existing commercial vendor of extension(s) that meet your needs.

Eric.

 


Thanks
Ragu.P

Reply | Threaded
Open this post in threaded view
|

Re: Subversion and JIRA integration

Dane Kantner

Also note that the pricing for new licenses will be going up a not insignificant percentage October 3rd -- https://www.atlassian.com/licensing/future-pricing   -- so if you are thinking about buying it you may just skip the trial :(



On Mon, Sep 30, 2019 at 7:35 PM Ragu Nathan <[hidden email]> wrote:
Thanks for your responses Eric and Dan,

So FishEye interfaces with JIRA and Subversion.
Do you have the trail versions of these tools ? I could try and see how it works or you have some sort of online demo for me to see how it works.

Your response is appreciated. 

Thanks 
Ragu.P

Sent from my iPhone

On Sep 30, 2019, at 5:06 PM, Dane Kantner <[hidden email]> wrote:

The actual Atlassian product you're looking for is called FishEye. It works with all major repos including SVN, Git, etc., and its primary purpose is exactly what you're wanting. This is a different license, and runs as a different service than Jira -- which could potentially actually make it cheaper in theory than if it were an actual straight up Jira add-on only since you can license it to a subset of your overall Jira users whom may actually need it.

FishEye is specifically meant for the purpose of integrating source control repositories into Jira. When you check an item in to SVN, as part of the checkin you would provide the Jira ticket # in the log, and then Fisheye indexes that, and then in turn Jira provides links/revision #s/etc. within the Jira ticket. If you then click that it will open in the FishEye interface and you can dive down further into what was checked, see the diff, etc., full source control, etc., in the Fisheye web interface.   Another Atlassian product, Crucible, ties-in to that then to allow you to do a standard code review workflow if you wish, but that is another addon beyond Fisheye even.

Anecdotal notes on this product are it works great but you should really make a good attempt at installing this on the same actual server your SVN server runs on, so you can access the repos by their file:// location -- the difference is 100x speed vs over the network w/ http/svn protocols, and may even be the difference between the product working and being able to index your repo or not. If you don't want to run it on your primary SVN, consider an active mirror sync to the box that fisheye then runs on and index that version locally.

-Dane

On Mon, Sep 30, 2019 at 1:35 PM Eric Johnson <[hidden email]> wrote:
Hi Ragu,

Your question is sort of a tricky one. Well, at least parts of it are. But here's an attempt at an answer.

On Sun, Sep 29, 2019 at 9:50 PM Ragu Nathan <[hidden email]> wrote:

Hi,

I would like to know the Subversion can be integrate with JIRA bug tracking tool.

Yes, but it depends on your requirements, and how many development resources you're willing to throw at it, if a commercial vendor doesn't provide it already.
 
Ex: I found an  issue in software coding and create a problem report to address root cause, analysis, documents updates , etc and I will use the JIRA to track all above, but Subversion is a configuration management tool to store data ( source code, documents, etc).

Subversion is a version control tool, not a configuration management tool. While it may certainly be possible to use Subversion in the manner implied, the definition of "configuration management" may lead to requirements that Subversion is less than ideal for.
 
Questions:
1. If I use the JIRA tool to address an issue , address all sort of analysis, proposed solutions, implementation details and I want to update the documents or source code in Subversion, is there any way to get into Subversion from JIRA? Not hyperlink. Real integrate environment. In this case I can check if any updates were made in to the documents or source code , which problem reporting # was used to fix the issue.

As I understand it, JIRA includes an extension API. It certainly should be possible to extend JIRA to get more detailed information about links into Subversion, without, as you indicate "hyperlinking".

There exist integrations into JIRA already for tighter coupling with Subversion, so you could start with those, to see if any of those meet your requirements.
 
2. Are both tools integrate together?

It is left to one's imagination. Both have APIs, so it is possible to add tighter integration to both. For details of how to integrate from Subversion's perspective, check out the "hook" documentation:


Atlassian definitely offers APIs from the JIRA side: https://developer.atlassian.com/server/framework/atlassian-sdk/
 
3. If so, how much would it cost for floating licence?

This mailing list isn't going to be a good source of information about that. And that assumes that you can find an existing commercial vendor of extension(s) that meet your needs.

Eric.

 


Thanks
Ragu.P