Bulk change the Bitbucket/Stash URL in Bamboo for all the jobs/plans

[hachdevopsissues]

Fellas,

We are migrating our Stash/Bitbucket repo from in house to a cloud environment this weekend and with migration the URL of the Stash/Bitbucket URL will change.

Following are a few questions, the answers to which we still haven't figure out yet:

• Will changing the application link to stash repo suffice for the job to use the new Stash repo? 
• Do we need to individually change the "Repository URL" for all the linked repo?

If we need to individually change the "Repo URL", is there a way we can change the Stash/Bitbucket URL in Bulk by running a SQL script on Bamboo database?

We have few repo that utilizes the application link and few which actually use an explicit "Repository URL", we are not that concerned for the former but are a bit concerned on how to seamlessly make this transition for the latter. 

Any help would be appreciated.

[Jeyanthan I]

Hi,

Will changing the application link to stash repo suffice for the job to use the new Stash repo?

It is not sufficient to recreate the application link.

Do we need to individually change the "Repository URL" for all the linked repo?

Not necessarily. You can do this directly on the database to perform a bulk update of the repository URL. We have an open feature request - BAM-18273 to make this change easier.

Below are the steps to follow in the meantime:

• Stop the Bamboo server.
• Run the below query.

  SELECT * FROM VCS_LOCATION WHERE 
          XML_DEFINITION_DATA LIKE '%<old-URL>%';
  

• Verify from the result if you have old entries in the XML_DEFINITION_DATA column.

•  Take a backup of the database just in case if something goes wrong.

• Run the below query to update those entries you found in the previous comment.

  UPDATE VCS_LOCATION SET XML_DEFINITION_DATA=REPLACE(XML_DEFINITION_DATA,'<old URL>','<new IPaddress/URL>');
  

• Re-run the select statement and confirm that you do not have any entries listed.
• Start the Bamboo server.
• You might want to resave al these repositories manually to recreate SSH keypair.

Hope that helps.

Cheers,
Jey