You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
So we have two stages: Build (CI) and deployment (CD)
Everytime after I run a build I got a number, for example, 123
When I start a new deployment, I set three environments:
the only difference betwen these environments are one environment variable , for example, I set below variables in the deployment job.
environment = dev
Now I found it is hard to get this simple job done. Because there is no source code checkout to check the commit in that build.
For example, when I run the deployment on build 123, I should see the source code only in that build. tomorrow, I have a new commit and run the build, and generate build 124
If I start the deployment again with same build number 123, it in fact deploys the latest commit (that's in build 124).
Bamboo ask me to do via Artifact, but I don't think that's the right way to do CICD.
So how can I do? any better way?
Can you describe a bit more about the tasks you are using in your deployment stage?
How are you accessing the code that was built within your build stage. Artifacts are generally the way that Bamboo moves built items that you which to save between jobs/stages/etc. So I feel like they gave you the correct advice, but I'd like to know more about what you are doing in your environment to understand why you do think that is the correct way to do things?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.