Deploying releases

Richard Isbell November 14, 2017

I was engaged by my dev team to do an SIA(security impact analysis) on their development environment,  They want to use Bamboo to publish their releases to the various environments,exactly as shown here - https://confluence.atlassian.com/bamboo/files/289277495/424411389/2/1398652922088/BambooDeploymentProjects.png

 

I am trying to find out how(port, protocol, etc) the code moves from the Releases stage to the Environments stage.  In searching this KB, I've seen mention to endpoint agents, SFTP, SSH, etc.  Can someone point me in the direction of some technical documentation that will provide the full picture?

 

Thanks for your time!

1 answer

0 votes
robhit
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 15, 2017

Hi Richard,

 

I am not sure why the middle man ("file server") is requred here
but you could directly connect bamboo to bitbucket repositories and the case where you want to achieve release management, bamboo has the triggers which will invoke the build in the bamboo whenever there is any change committed to the bitbucket repository

so the flow could be like this:
1. Changes made to bit repo
2. Bitbucket sends an event to Bamboo (by using the triggers in Bamboo. And you have to use application links to connect bamboo and bitbucket with each other)
3. Bamboo triggers the build.
4. Upon successful build (or your condition set), relevant deployment will be triggered to perform the release.

 

Some docs which can be useful:

https://confluence.atlassian.com/bamboo/triggering-builds-289276897.html

https://confluence.atlassian.com/bamboo/repository-triggers-the-build-when-changes-are-committed-289276902.html

https://confluence.atlassian.com/bamboo/deployment-projects-338363438.html

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events