Bamboo checks out old revision and ignores latest commit

Summer X

Hi,

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.

Przemek Bruski

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.