You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have a situation where we want to specify the tag used for the build. What variable does the Source Code Checkout task use to decide which commit to checkout?
Please add a "tag" input box for the "Source Code Checkout" task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the end we had to remove the "Source Code Checkout" task and instead run two command tasks, one to fetch and the other to checkout. These used the system git executable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you run plan you can specify SHA commit.
Choose Run customised option at Run dropdown list
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our use case is not for the plan level, but at the stage/task level. This arrises when we cut a release and we need to do follow up work against the tagged release commit. The plan commit is looking at the commit before the release and master is now the commit after the release.
Also, this question is relevant for if we have builds that are not manually triggered.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.