Bamboo checks out old revision and ignores latest commit


I have two jobs set up for a build. The first job checks out trunk manually (using sliksvn 1.7 CLI client in batch script, not bamboo's checkout). Changes a version file, then commits back (again using sliksvn CLI client in a batch script). Assume at this time, the revision of trunk changes from 100 to 101. (files checked-out to job1 folder)

Now in second job, I use Bamboo checkout (files checked out to job2 folder). However, Bamboo only checks out revision 100. It ignores revision 101, which is committed by job1. So I end up building out of date files.

Why is this happening? Thank you in advance.

1 answer

1 accepted

0 votes
Accepted answer

The revision that will be used by all Jobs in a Plan is determined before the Plan is run so that all Jobs consistently build the same revision.

What you could do is to have these two jobs in separate stages and pass an artifact between them that would define the revision to checkout for the second job.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,906 views 7 10
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you