-
Bug
-
Resolution: Fixed
-
Medium
-
4.3, 5.7.2, 5.8.1
-
Severity 2 - Major
-
2
-
Environment: CBAC (4.3-M3 build 3306)
We changed the shared repositories that the Confluence builds use and updated the repository URL.
The existing branch build plans are still using the repository information that was current when the branch plan was created.
Because the original repository was removed most of the branch builds now fail and Bamboo keeps trying to retrieve repository information from the repository that doesn't exist anymore.
- is related to
-
BAM-18253 Improve other repository types such as GitHub to make use of linked repository inheritance
- Closed
- relates to
-
-
- Closed
-
-
- Closed
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BAM-12330] Plan branch source repositories should be updated when the shared repository for the main plan gets updated
I believe we have this issue now, after I migrated our Stash repository in preparation for an upgrade to bitbucket. All the RepositoryUrl metadata in the existing branches has the old host. Anyone sort out a workaround for this? Can I clear remote agent cache, similar to trying to remove all the bamboo server cache (Repostory Settings > Git) xml-data\build-dir_git-repositories-cache. I still have tons of branches here referencing an old hostname. Researching options now.
Thank you!
We're also experiencing this (or a related) bug, but we're not using branch plans for a particular build plan, so the workaround listed at https://support.atlassian.com/browse/BSP-17169?focusedCommentId=5588964&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-5588964 doesn't work us. Updating the plan's repo settings seem to have no effect, nor does creating a new repo for the plan. When run, the build is still pointing to the old repo.
Is there anything we can do outside of completely deleting the entire build plan and starting over? Will the cached refs still be in there?
In 5.14 we are introducing a feature that allows plan branches to override just the branch, while the rest of the configuration is inherited (rather than copied) from the master plan. This feature however requires changes in each repository plugin and thus is now only suported for Git, Bitbucket Server (Stash) and Subversion repository types. We have plans to implement it for other Atlassian provided repository types in near future.
There's an upgrade task that introduces inheritance in existing data but it won't fix data that is already broken since we can't tell if difference in configuration is intended or not.