Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bamboo checks out old revision and ignores latest commit

Summer X
Contributor
August 10, 2012

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.

1 answer

1 accepted

0 votes
Answer accepted
Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 10, 2012

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
TAGS
atlassian, confluence administration certification, atlassian certified professional, confluence admin for cloud, atlassian learning, confluence training, confluence certification exam, confluence cloud admin, admin credential, atlassian certification

Become a certified Confluence admin today! 📖

Stand out as a skilled Confluence Cloud administrator. The Confluence Administration for Cloud certification proves you can configure permissions, manage site and space settings, and monitor activity—ensuring secure, effective collaboration for your team.

Start here
AUG Leaders

Atlassian Community Events