Migrating Stash Server w/ Integrated JIRA

I will shortly be migrating our 10 user Stash server to a new 500 user Stash server on a different host. I saw this article: https://confluence.atlassian.com/display/STASH/Migrating+Stash+to+another+server . Our old Stash server is integrated with our JIRA server - how can I mass-update all of the JIRA Source Tab links to reference the new Stash server? Or, will all the links be automatically fixed when I update the Application Link to connect to the new Stash?

2 answers

This widget could not be displayed.

Hi, considering it's a migration, it'll be the "same" Stash. If you're keeping all the data - database etc, it'll have the same IDs etc. Will the URI even change with the migration? If not, nothing to worry. If the URI changes and the old one won't be running again, JIRA will let you relocate it.

The URL for the new Stash server will be different from the old. We are planning on moving all of our repositories from the old Stash to the new one. We will also be leaving our old 10 user Stash server online (for testing other things).

The URL for the new Stash server will be different from the old. We are planning on moving all of our repositories from the old Stash to the new one. We will also be leaving our old 10 user Stash server online (for testing other things).

This widget could not be displayed.

I recommend using a second, generic DNS name (depending on your LAN/WAN). This name is initially set to your current stash server. After creating it, update your Jira (and other products) servers to use the generic name.

For example, when I run a nslookup on the generic name, let's say: enggit.{company-acronym}.com (for Engineering Git), it responds that the canonical name is the hostname and IP address of the actual server. Our IT dept. handles the network stuff, so I can't provide more detail.

When all is ready, stop the current stash server, replicate (see various documents on the subject) your data to the new server, fire it up, verify it, then change the generic DNS name to the new server hostname. I also suggest a test run before the "red flag" date.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

76 views 1 0
Join discussion

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