nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

BAMBOO get commits that triggered build

andreiverdes

Hi!

Is there a way to get the git log with the commits that triggered the build from the command line inside the build agent?

I'm building an Android app with gradle and push it to Crashlytics alongside with a changelog.txt file. I would like to add those commits to a changelog.txt per build so I would know what that build is about.

Thanks!

PS: Sorry if I'm not offering enough details, it's my first question here laugh

Accepted answers

Alex Soto_a4l4ig

If you're submitting things via a script, you can use bamboo variables to get the build's revision and get the commit log and write it to a file.

Here's an example using git:

git log ${bamboo.planRepository.previousRevision}..${bamboo.planRepository.revision} --oneline &gt; ./commits.txt

Other bamboo variables: https://confluence.atlassian.com/display/BAMBOO/Bamboo+variables

All comments

Jaime S

Hi, Andrei.

I'm not sure if you can get this information from the agent within the instance, but this information is available under the 'Commits' tab in Bamboo itself in the build information, if that's helpful.

Kind regards,
Jaime Kirch da Silveira
Atlassian Cloud Support

Alex Soto_a4l4ig

If you're submitting things via a script, you can use bamboo variables to get the build's revision and get the commit log and write it to a file.

Here's an example using git:

git log ${bamboo.planRepository.previousRevision}..${bamboo.planRepository.revision} --oneline &gt; ./commits.txt

Other bamboo variables: https://confluence.atlassian.com/display/BAMBOO/Bamboo+variables

andreiverdes

This seems to do the trick! Thanks!

shubham patni

I tried following but this say "log: command not found"

gitlog=git log ${bamboo.planRepository.previousRevision}..${bamboo.planRepository.revision}

What am I doing wrong here ?

faheem.armanyous@cnb.com

The variable $bamboo.planRepository.revision only revers to the commit hash of the default repository in the plan. not the commit that actually triggered the plan in a multiple repository plan configuration. in my scenario the actual variable for revision is

$bamboo_planRepository_9_revision

is there a variable for the repo name or the exact commit that triggered the plan without having to figure out the repository position. ?

Thanks

Davide Ceccato

this information is available under the 'Commits' tab in Bamboo itself in the build information

Any REST API for that?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bamboo