Hi, I though I could use the Rest API for deployment but I'm having difficulties understanding the authentication method needed to achieve that and how to set it up
Does this work as well with the builds API as I'm getting forbidden responses using the build URL: rest/builds/0.1/bulk
Yes that's right.
To get rid of Forbidden - Double check - Authentication / permissions and the Deployments features.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To integrate your ArgoCD pipeline with Jira issues via the Jira REST API, authentication setup is essential.
For Jira Server/Data Center, choose between Basic Authentication (less secure) and OAuth (more secure). For Jira Cloud, generate an API token through the Atlassian API token management portal.
https://id.atlassian.com/manage/api-tokens
To authenticate:
In your ArgoCD pipeline:
Example using curl for Jira Cloud:
bash
curl -D- \
-u your-email@example.com:your-api-token \
-X PUT \
-H "Content-Type: application/json" \
https://your-domain.atlassian.net/rest/api/3/issue/ISSUE-KEY \
--data '{
"fields": {
"customfield_10000": "Deployment completed"
Replace your-email@example.com, your-api-token, your-domain, and ISSUE-KEY with your actual values
To learn more about authentication:
Solved: How to authenticate to Jira REST API
Jira Align and Authentication Methods (Jira Connec... - Atlassian Community
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
403 errors can arise from several common causes.
Firstly, incorrect credentials or insufficient permissions can prevent authorized access, triggering the error.
Furthermore, API token issues specifically affecting Jira Cloud integrations can also lead to 403 errors. Another possible cause is using an incorrect API endpoint, which can disrupt communication.
Likewise, network or firewall restrictions may block requests, resulting in the error.
Best Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.