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
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
I can't find a way in the yaml spec reference to checkout a specific branch of a (linked) repository. Creating an extra linked repository for each branch isn't a clean solution in my opinion.
Does anyone know about this?
We ran into a similar problem, where we wanted to checkout specific tags or branches of dependencies, depending on the versions used in the main project that is being tested.
I did find a solution, but it is not exactly "clean" - in fact it is really complicated given the simplicity of what I wanted to achieve.
At the start of the build I defined a task, which parses the version of the dependency from the main build and exposes it as a "result variable". In our case they are all maven projects, so we use the Maven Pom Value Extractor plugin for this part.
Then I have defined stages to build each of dependencies. The first task in each of these stages uses a Script task to manually checkout the correct tag / branch of the dependency.
We use java specs so I don't have yaml version to hand, but the basic format is like this:
Stage 1 : Check dependency versions
Stage 2: Build dependency x
...More stages for other dependencies
- Build main product we want to test.
Oh, forgot to actually answer the question:
First we have a checkout task, which checks out the dependencies master branch.
Then, we have a script task with contents similar to below:
git branch -a
git checkout $EXPECTED
CURRENT=`git rev-parse --abbrev-ref HEAD`
if [ "$CURRENT" == "$EXPECTED"];
echo "Now on branch $CURRENT"
echo "On branch $CURRENT, either $EXPECTED does not exist or repo cache outdated
- We had to select the option: "Fetch Whole Repository" on each linked repo
- We had to make sure to checkout each dependency into it's own working directory (and set the script task's working directory to match the dependency in question
Try sth. like this (requires Bamboo 6.10 or later)
name: Plan name
- Default stage:
- Default job