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.
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.
Please, make sure the Fisheye URL has been updated in:
Rafael P. Sperafico
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.
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%';
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%';
Rafael P. Sperafico
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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!
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