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,555,974
Community Members
 
Community Events
184
Community Groups

Uploading Bitbucket pipeline artifacts to sharepoint

Edited

I've been searching for a way to upload the pipeline artifacts to SharePoint using the SharePoint API. However, I could not find anything about how to do that from bitbucket side. The artifacts are already being deployed and can be found in the download section. In the Atlassian support it says " there is a way to send your artifacts to 3rd-party storage and create a link in your commit view, using the Bitbucket build status API." But the link they have provided does not provide a clear approach.

How can I use these artifacts and upload that to the SharePoint or any 3rd party storage?

2 answers

@yashoda.chandrasekara did you get this working?

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 15, 2021

Hi @yashoda.chandrasekara and welcome to the community.

Have you tried using a Sharepoint API call during the Pipelines build?

You can edit the bitbucket-pipelines.yml file and either create a new step that executes this API call or add the API call in one of the steps where these artifacts are available.

If you need to authenticate in order to execute the API call, you can define variables for any passwords/tokens (and make them "Secured" so they won't be visible in the Pipelines log) and use them in the API call.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events