Question re Upgrading SVN, JIRA and a Windows & Linux Environment

Hi,

We're currently running SVN, FishEye, Eclipse and JIRA on a Windows platform. We are planning to run everything on a Linux platform. I know I asked questions yesterday regarding upgrades but I needed to clarify that in addition to upgrading these tools, is there anything we need to be aware of that might be 'gotchas' before we migrate to Linux?

Our current plan as of today's meeting is to:

1. Make a copy of our current VM that is hosting all our current CM tools and from there perform an upgrade of JIRA in our test environment.

2. One assumption that was made at today's meeting is that by upgrading JIRA that we won't have to add another pre-commit hook since we already have that in place with our current JIRA and SVN. Is that true?

3. Once we have successfully upgraded JIRA and integrated with our current Windows SVN then our next step was going to be to migrate this to the later SVN version that would be running on Linux.

4. I don't suppose it's possible that our current JIRA instance could be pointed to more than 1 SVN repository where one is in Windows and the other SVN is on Linx? That was a question that came up today too. The reason it came up is that we are providing O&M and our code is in our current SVN that's on Windows but our new development work was to go in to a later version of SVN that's on Linux..

Thanks in advance for your help!

Melissa

2 answers

This widget could not be displayed.

Hi,

Can you explain what you are currently trying to achieve with your pre-commit hook?

You will need the JIRA SVN plugin - https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.ext.subversion to do what's been described. You can definitely add different repositories from different locations.

Hi Harry,

It appears this is now moot as our lead developer was able to add the pre-commit hook to our new instance of JIRA that's now integrated with our newer version of SVN. I'm not sure how he did it but I know he was going to look at how it was set up with our older JIRA/SVN that we're still using.

Thank you for the answer you provided though as this is appreciated.

Respectfully,

Melissa

This widget could not be displayed.
  • If you are using Fisheye, then you need not connect JIRA directly to SVN.
  • Regarding point 2 can you explain it a bit more as requested by Harry Chan, are you talking about Commit Acceptance plugin?
  • If you are using JIRA to SVN mapping directly in JIRA, AFAIK, per project you can associate only one repository, but that restriction goes away if you have Fisheye/Crucible which enables you to use projects which can map to multiple repositories per project.

Hi Renjith,

We plan on adding Fisheye at some point to our newer version of JIRA (which is now integrated with our newer SVN) but will this cause any kind of conflict once we add Fisheye since we already have a pre-commit hook in place?

Thanks and let me know.

Melissa

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

1,345 views 8 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you