Hello All,
We have a build jobs running for our project which create certain artifacts. These artifacts constitute the various deliverable of a release. We wanted to know if there is a way these artifacts can be uploaded to the linked confluence space for our project.
The idea is to have a release note page which has all the uploaded the artifacts from bamboo and the JIRA tickets from the current release.
Please do let me know if its possible internally or if we have a plugin that could do this for us.
TIA,
~Aby
Use a task in a deployment environment to create the page and upload the files using the REST api. Should be straight forward.
Hello Steven,
Thanks for addressing this. We do not have a deployment environment or a deployment project.
What we have is a build project with stages and our scripts added to these stages. From what I understood we can still have a script as a part of the stage which accesses the Confluence REST API and uploads the artifacts generated by the build to a confluence page.
Please correct me if I am wrong. Also please do suggest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would suggest handling this in a Deployment Project attached to your Build Plan. This way only successful builds will deploy to Confluence.
Regardless, the approach is the same in a deployment project or build plan -- They both use Tasks.
The Script Task would allow you to select a script that has the appropriate calls. You can call the createContent endpoint with the XML for the page, and then call the createAttachment endpoint with all the files you're adding.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Steven,
Thanks for your inputs.
Is it necessary to have a Deployment project additionally. Can this script be added to an existing build plan?
I already have a running build plan which validates the bitbucket code.
TIA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Regardless, the approach is the same in a deployment project or build plan -- They both use Tasks.
Yes, as stated the script just needs to be ran. Whether or not that is a buildplan or a deploymentplan is up to you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.