nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Trigger Jenkins builds using Jira Automation

mayank goyal_2hboxb

Hi Everyone,

I am trying to trigger Jenkins build using Jira Automation, but it's failing. I am getting "No valid crumb was included in the request" error even after passing the Jenkins-Crumb header.

Configuration:

Screenshot 2021-07-03 160617.png

Error:

Screenshot 2021-07-03 160932.png

Also, I mention that when i try the same request using Talend API tester It works fine.

Screenshot 2021-07-03 161414.png

Accepted answers

Dario B

Hello @mayank goyal ,

Welcome to the Atlassian Community!

According to the Jenking Remote Access API documentation page, basic authentication with username and api-token has to be preferred over crumbs for CSRF protection:

Remote API and security

When your Jenkins is secured, you can use HTTP BASIC authentication to authenticate remote API requests. See Authenticating scripted clients for more details.

CSRF Protection

Note: API tokens are preferred instead of crumbs for CSRF protection.

Also, according to the Authenticating Scripted Clients, the content-type header is not needed:

Shell with curl
The curl command is available for most operating systems including Linux, macOS, Windows, FreeBSD, and more.
curl -X POST -L --user your-user-name:apiToken \
    https://jenkins.example.com/job/your_job/build

Therefore, can you kindly do the following and let us know the results?

Create an Api Token in Jenkins
Send a REST API call using Curl like in above example
If the call fails check what went wrong, otherwise configure the Send Web request automation action the same way and run it
Trigger the Automation Rule and check if this time is succeeding. Provide the outcome otherwise.

Cheers,
Dario

All comments

Dario B

Hello @mayank goyal ,

Welcome to the Atlassian Community!

According to the Jenking Remote Access API documentation page, basic authentication with username and api-token has to be preferred over crumbs for CSRF protection:

Remote API and security

When your Jenkins is secured, you can use HTTP BASIC authentication to authenticate remote API requests. See Authenticating scripted clients for more details.

CSRF Protection

Note: API tokens are preferred instead of crumbs for CSRF protection.

Also, according to the Authenticating Scripted Clients, the content-type header is not needed:

Shell with curl
The curl command is available for most operating systems including Linux, macOS, Windows, FreeBSD, and more.
curl -X POST -L --user your-user-name:apiToken \
    https://jenkins.example.com/job/your_job/build

Therefore, can you kindly do the following and let us know the results?

Create an Api Token in Jenkins
Send a REST API call using Curl like in above example
If the call fails check what went wrong, otherwise configure the Send Web request automation action the same way and run it
Trigger the Automation Rule and check if this time is succeeding. Provide the outcome otherwise.

Cheers,
Dario

mayank goyal_2hboxb

Hey Dario!

Thanks a lot, this worked really well. :-)

I want ask a question: Last time when I was trying with username:password it was failing in jira automation but succeeded with Talend API tester.

Dario B

Thanks for your quick reply @mayank goyal ,

However, I am not sure I understand what the question is, can you kindly try to reformulate?

mayank goyal_2hboxb

Yes sure.

When I was trying to trigger the Jenkins job using username:password it was failing in Jira Automation (reason I asked this question). But when I tried to trigger the jenkins job using same way i.e username:password in Talend API tester it worked (screen-shot attached below).

So why username:password authorization is failing in Jira Automation while it's working fine in Talend API test.

EDIT: In the Talend API tester I am able to trigger the jenkins job even without username and password (only with Jenkins-Crumb)

I hope question is clear this time. Please let me know if it's unclear.

Screenshot 2021-07-03 161414.png

gnanavelu_murthy

@Dario B @mayank goyal and @charleslcso

I am also not able configure this automation webhook fires 503 error. Dont know where i missed.

Server: squid

Mime-Version: 1.0

Date: Thu, 10 Mar 2022 20:03:36 GMT

Content-Type: text/html;charset=utf-8

Content-Length: 3261

X-Squid-Error: ERR_DNS_FAIL 0

Vary: Accept-Language

Content-Language: en

Dario B

The error you get is "service unavailable" and therefore this doesn't seem to be authentication related.

Actually, the error returned by squid is DNS related:

ERR_DNS_FAIL

Are you actually able to send the same request using Curl?

karthik.c

@gnanavelu_murthy @Dario B

We tried from Postman and able to trigger build in jenkins. Getting error only when triggered from JIRA Cloud site.

Dario B

Not providing any detail about what does not work is not helping us to help you

However, as a starting point, you may want to check the error message returned by Jenkins.

Mark Rekveld - Marvelution

For those this looking, the Jenkins Integration for Jira app supports triggering a build via a manual issue action as well as via a Workflow Post Function. Check out the docs here: https://jjc.marvelution.com/docs/features/trigger-build

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

webhook

atl-gruland

jenkins

automation