Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo "Source Code Checkout" references old commit


So, I have a Bamboo job that consists of a few tasks:

- A series of SSH tasks that performs the build for my project. The last step wraps everything up in a .zip file and commits/pushes that .zip file to BitBucket.

- Source Code Checkout

- Maven, which basically takes the .zip file and publishes it as an artifact somewhere else

The problem I'm having is that the version of the published artifact is always one iteration out of date, because Source Code Checkout appears to only care about the state of the repository when the job is initiated. It misses the commit/push done at the end of the SSH tasks. The next run of the job picks it up. So, what's the most elegant and correct way to fix this?

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events