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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

In Bamboo, how can you determine which git commit generated a given build artifact?

I want work backwards from a build artifact (eg: .hex file from compiler output)  generated by Bamboo and find the associated .git commit reference used to build this artifact.

2 answers

Hi @Phillip Matthews,

You could iterate over the JOB that published the artifact by consuming a REST API endpoint http://myhost.com:8085/rest/api/latest/result/{projectKey}-{buildKey}-{buildNumber : ([0-9]+)|(latest)} [GET]

As an example, you could run:

# replace USERNAME with a user who has VIEW permissions over given plan
# replace http://localhost:8085 with Bamboo's Base URL
# replace PROJ-PLAN-JOB1-1 with buildResultKey. Please refer to Bamboo Variables -
https://confluence.atlassian.com/x/nwQ_EQ - for more explanation

curl -k -u USERNAME \
-H 'Content-type: application/json' \
-H 'Accept: application/json' \
-X GET http://localhost:8085/rest/api/latest/result/PROJ-PLAN-JOB1-1?expand=vcsRevisions&expand=artifacts

As result, you will find the commit information under vcsRevisions.vcsRevision[max-result - 1].vcsRevisionKey:

{
    ...
    "vcsRevisions": {
        "size": 1,
        "expand": "vcsRevision",
        "vcsRevision": [
            {
                "repositoryId": 1605634,
                "repositoryName": "My Repository",
                "vcsRevisionKey": "defd4d397004415f683af6f356f59d77c04a9a10"
            }
        ],
        "start-index": 0,
        "max-result": 1
    }
    ...
}

and the artifacts available to build result under artifact[1] onward.

{
...
    "artifact": [
        {
            "name": "Build log",
            "link": {
                "href": "http://localhost:8085/download/PROJ-PLAN-JOB1/build_logs/PROJ-PLAN-JOB1-1.log",
                "rel": "self"
            },
            "producerJobKey": "PROJ-PLAN-JOB1-1",
            "shared": false
        },
        {
            "name": "TXT",
            "link": {
                "href": "http://localhost:8085/browse/PROJ-PLAN-1/artifact/shared/TXT/",
                "rel": "self"
            },
            "producerJobKey": "PROJ-PLAN-JOB1-1",
            "shared": true,
            "size": 31,
            "prettySizeDescription": "31 bytes"
        }
    ]
...
}

Please, refer to the following documentation for further information:

Hope the information provided help you somehow.

Kind regards,

Rafael

0 votes

There's build variable planRepository.1.revision which contains revision hash. You can use it to generate artifact name or content

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 7.1 is here and is packed with value!

I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...

943 views 4 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you