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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,467,448
Community Members
 
Community Events
177
Community Groups

Checking out consistent git revision across stages

I have a stage for building my application, and another stage for running integration tests. As I understand it, each job that needs the source must checkout the source again, so what happens if someone commits during the build stage? Will the integration step phase include the newest commit? Or will it somehow be locked to the revision of the source used in the build stage? 

1 answer

Ok, I think the answer is that the revision number is locked for the whole build of a plan. I haven't found this explicitly stated in the documentation, but I did find the following which implies this is the case:

"If the child build uses the same source as the parent build (for example, the Subversion URL is the same), the child build will be forced to check out the same revision of source code as the parent build. This ensures that builds are consistent when triggering one build from another."

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events