Updated web repository link (FishEye) in Bamboo not changed for old commits

We recently moved around some servers and IP addresses changed etc. In Bamboo, under the "Repository Settings" in the main administration settings, as well as in each individual plan's repository settings, I changed the Web Repository URL to point to the new location of FishEye.

It used to be something like http://192.168.40.40:8060, now it's http://fisheye.company.com (this is running behind an IIS ARR proxy).

For new builds since the above change, Bamboo is fine - any commits/changesets show up correctly under the "Commits" tab of a build, and the links point to the correct (new) URL.

However for old builds, Bamboo is still pointing to the old URL (http://192.168.40.40:8060/browse/repo/trunk/etc...).

Is there a way to get Bamboo to "refresh" these links and re-point them to the new location for FishEye?

We're using Bamboo 5.13.2.

Thanks!

3 answers

This widget could not be displayed.

Hello Alexis,

Please, make sure the Fisheye URL has been updated in:

  • Plan configuration >> Repositories >> <Subversion repository> >> Advanced options >> FishEye URL
    image2016-11-24 16:42:49.png 
  • Branches >> <Subversion branch> >> Source repository >> Advanced options >> FishEye URL
    image2016-11-24 16:44:57.png

Kind regards,
Rafael P. Sperafico

This widget could not be displayed.

Rafael,

I should have mentioned this in my original post - I did make the change in the settings for all our build plans (as well as in individual branch builds under each plan). Yet the new links only seem to apply to builds completed after these changes, and none of the older builds.

-Alex

This widget could not be displayed.

Hello Alexis,

Please, run the following SQL statement against Bamboo's database and raise a support request with its response along with mentioning this link https://answers.atlassian.com/questions/44354497:

select B.FULL_KEY as PLAN_KEY,
       B.TITLE as PLAN_TITLE,
       VL.PLUGIN_KEY as REPOSITORY_TYPE,
       VL.VCS_LOCATION_ID as REPOSITORY_ID
  from VCS_LOCATION as VL
  join PLAN_VCS_LOCATION as PVL on PVL.VCS_LOCATION_ID = VL.VCS_LOCATION_ID
  join BUILD as B on PVL.PLAN_ID = B.BUILD_ID
  join BUILD_DEFINITION as BD on B.BUILD_ID = BD.BUILD_ID
 where VL.XML_DEFINITION_DATA like '%192.168.40.40%';

information The SQL statement above will return all PlanKey and repository ID that has 192.168.40.40 as reference.

select VL.VCS_LOCATION_ID as REPOSITORY_ID,
       VL.PLUGIN_KEY as REPOSITORY_TYPE
  from VCS_LOCATION as VL
 where VL.XML_DEFINITION_DATA like '%192.168.40.40%';


Kind regards,
Rafael P. Sperafico

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
Published 6 hours ago in Marketplace Apps

The 7 hacks of highly successful automation

...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...

38 views 0 8
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