Ok, I'm pretty new to Bamboo, and I'm having a hard time deploying just the way I want.
Right now, I have a build plan that polls my git repo for changes in a branch ("development") and does:
2. script (removes files that I don't want to deploy)
There's a shared artifact (called "DevelopmentArtifact") and, when this build finishes, I can see the content of this artifact is correct (the files I don't want to deploy are not there).
This triggers a deploy configuration for a QA environment. The tasks defined in this environment are:
1. Artifact Download (pointing at "DevelopmentArtifact")
2. SCP Task
When I read the deployment log, I can see it is actually deploying the full development branch, not the "filtered" artifact. All the files that I removed with my script on build are back there!
Any ideas why would that happen?
I have both "development" and "master" branches configured in the plan, and both the Build and Deploy plans show the "development" branch label. But there is no version control checkout in my deployment configuration, so why would it ignore the artifact and get all the files instead?
Let me know if you need more info to understand the problem.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot