Sure!
We have all of our source in Bitbucket cloud and then a local bamboo server. The checkout speeds from Bitbucket cloud to the UK are awful so when we upgraded to premium for the access checks I went to take advantage of the smart mirroring option that comes with it.
I set up a local smart mirror successfully and its mirroring all of our Bitbucket projects locally. I went to add a linked server to bamboo and was surprised to find it didn't work. What this means is I have to go through almost 700 various plans + plan branches, change them to use Git, work out the url as its different for every project, manually enter the branch name and manually enter credentials.
As you can imagine, this is an enormously manual process which I'm unlikely to ever complete. I was expecting to enter the credentials once for the linked server and then have easy drop downs for picking projects and branches. This is ignoring the fact that we also won't benefit from web hooks for automated builds and have to keep relying on repository polling
Sure!
We have all of our source in Bitbucket cloud and then a local bamboo server. The checkout speeds from Bitbucket cloud to the UK are awful so when we upgraded to premium for the access checks I went to take advantage of the smart mirroring option that comes with it.
I set up a local smart mirror successfully and its mirroring all of our Bitbucket projects locally. I went to add a linked server to bamboo and was surprised to find it didn't work. What this means is I have to go through almost 700 various plans + plan branches, change them to use Git, work out the url as its different for every project, manually enter the branch name and manually enter credentials.
As you can imagine, this is an enormously manual process which I'm unlikely to ever complete. I was expecting to enter the credentials once for the linked server and then have easy drop downs for picking projects and branches. This is ignoring the fact that we also won't benefit from web hooks for automated builds and have to keep relying on repository polling