So I've got Bamboo up and running on my project, and I've got it doing "releases" into Artifactory.
I really want Bamboo to manage the deployment pipeline as well, but there are a couple things I'm not clear on. First, our configuration management team uses RPMs as the unit of deployment. I know I could build an RPM and pass that along as an artifact, but then it doesn't go into Koji.
Here's what I really want (this is a non-java but totally mavenized project), somebody tell me if it's crazy:
Can somebody point me in the right direction with this one? Do we have to give up RPMs to use the deployment part of the tool?
I did this by scripting the pull from artifactory using cURL to get the artifact. Then a ssh script to the target from a bamboo script task that runs a yum install of the rpm .
We later modified it to run a CHEF script for the install and pulled everything out of the pipeline except a release promotion of the rpm to another yum repo in artifactory.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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