One of the builds on our Bamboo server has FishEye configured as a web repository. The repository in question makes use of the "svn:externals" property to include another repository and the build is set to detect changes to "svn:externals".
The problem is that when these changes are detected by Bamboo, the changeset URL's are all wrong, i.e. they don't point to a valid location in FishEye. For some reason, FishEye doesn't follow the "svn:externals" property (i.e. doesn't show the contents of the external repository) and there doesn't seem to be a configuration option to do this.
How can we get FishEye to show the contents of any repository included using the "svn:externals" property?
Thank you for the quick answer. I was just wondering though, is Bamboo the place for this improvement, or should FishEye be configured so that it follows these external repositories and makes them seamlessly available to Bamboo? i.e. Bamboo doesn't even realise that one of the directories in the repository is actually an "external"
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot