We are having two Build projects which has some build plans and we are always running a clean checkout for all plans.
We are using Build Number stamper plugin to generate "build-number.txt". This plugin runs as a pre-build action.
In Project 1 pre-build action runs after "Checkout Default Repository" task and hence our generated build-number.txt is retained
In Project 2 pre-build action runs at the start i.e. before "Checkout Default Repository" and since we always do a clean build. The task 'Checkout Default Repository" removes build-number.txt.
I have looked in every tab and in miscellaneous tab in the corresponding Job and I cannot find were this behavious is defined.
Appreciate if someone please shed some light on this
The pre-build action are deferred after Checkout Task if this is the first task in the Job.(more precisely it is executed before the first task which is not 'initialising task', so if you have 2 checkout tasks at the beginning the pre-build action would be executed after both of them. But if you put script task at the top it is executed before it)
In your case the solution would be to move disabled task down the pipeline (since you don't use it anyway).
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot