We had an issue with fisheye recently and had to create a new perforce repository index with a different name, then delete the old one. That issue is now resolved, but the problem now is that all the previous links in bamboo to Code Changes (which would normally take us to the Fisheye repository web viewer) are broken, because the RUL's still point to the old non-existant repository index.
Is there any way to fix this?
I'm assuming that these url's are hardcoded in the DB, and I'd need a postgres script to patch our database. Am I correct? If so, can anyone sugfgest such a script?
Fisheye 2.8 / Bamboo 4.2.0 / Postgres backend for both
The URLs can be fixed via the UI. Please, see the screen shot in the following page:
Basically, Bamboo does not store the links to Fisheye in the DB. It always use the information from the page above to build the URLs when a page is rendered (Fisheye URL + Project Name + Repo Path + Build Revision). By building and calling this URL, Bamboo is able to open the correct revisions in Fisheye.
Please, let me know if this is the information you need.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot