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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,593
Community Members
 
Community Events
176
Community Groups

How do I get artifacts with the REST API?

I'm trying to write a script to download the artifacts for the most recent build of a particular plan. I can see in Bamboo that this build has artifacts, but the response from the REST API shows none. Is there something I'm doing wrong? I'm using Bamboo 4.0.1

$ curl 'http://my-bamboo/rest/api/latest/result/MRPRJ-MYPLAN?expand=results\[0\].result'
# snip
  <artifacts size="0" max-result="0" start-index="0"/>

3 answers

1 accepted

4 votes
Answer accepted
JamesA Rising Star Apr 30, 2012

Are you sure you don't want to use the Job key instead of the Plan key? The query you are making to the rest api will only show the artifacts which have been Shared.

That was it! The REST API documentation didn't mention using job keys, so I didn't think about that. Thanks!

Hi David,

I am new to REST API and looking for this option.

Can you please help me with the command to get artifact using either build number or release id ?

Bamboo Command Line Interface has the getArtifact action which handles the REST stuff for you, but you will still need to do as James says to either make it shared (easiest) or access by job.

Thanks for the suggestion.

Is it visible without logging in? Maybe you can try with a username/password?

curl -u userid:secret ...

Yes, it is visible without logging in. Also tried with username/password, same result.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events