Curl script to invoke automation trigger does not work

Tejas Shah April 21, 2020

I am trying to create an automation rule in Jira that transitions Issues from one status to next based on an incoming webhook. The rule works fine when I make the call using postman But it does not work when invoked from a curl script on jenkins. 

The response returned is 200 OK but when I check the audit trail on Jira for the automation rule I do not find any requests

 


JIRA_ISSUES='ECO-26074'
curl -v -X POST -H 'Content-type: application/json' --data "{\"issues\":[${JIRA_ISSUES}]}" "https://automation.codebarrel.io/pro/hooks/d817e8bff0ef3ea863a1ba92856ebeb54733b92f"


+ JIRA_ISSUES=ECO-26074
+ curl -v -X POST -H 'Content-type: application/json' --data '{"issues":[ECO-26074]}' https://automation.codebarrel.io/pro/hooks/d817e8bff0ef3ea863a1ba92856ebeb54733b92f
Note: Unnecessary use of -X or --request, POST is already inferred.
* Uses proxy env variable no_proxy == 'lvmita-back01n.adm.lvm.cvf'
* Uses proxy env variable https_proxy == 'http://proxy.srvc.cvf:3128'
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 10.175.20.51...
* TCP_NODELAY set
* Connected to proxy.srvc.cvf (10.175.20.51) port 3128 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to automation.codebarrel.io:443
> CONNECT automation.codebarrel.io:443 HTTP/1.1
> Host: automation.codebarrel.io:443
> User-Agent: curl/7.62.0
> Proxy-Connection: Keep-Alive
>

0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0< HTTP/1.1 200 Connection established
<
* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: none
CApath: none
* loaded libnssckbi.so
* CONNECT phase completed!
* CONNECT phase completed!
* ALPN/NPN, server did not agree to a protocol
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* subject: CN=*.codebarrel.io,OU=PositiveSSL Wildcard,OU=Domain Control Validated
* start date: May 01 00:00:00 2018 GMT
* expire date: Jun 27 23:59:59 2020 GMT
* common name: *.codebarrel.io
* issuer: CN=COMODO RSA Domain Validation Secure Server CA,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB
> POST /pro/hooks/d817e8bff0ef3ea863a1ba92856ebeb54733b92f HTTP/1.1
> Host: automation.codebarrel.io
> User-Agent: curl/7.62.0
> Accept: */*
> Content-type: application/json
> Content-Length: 22
>
} [22 bytes data]
* upload completely sent off: 22 out of 22 bytes
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 0
< Connection: keep-alive
< Date: Tue, 21 Apr 2020 16:20:17 GMT
< x-amzn-RequestId: 8b7164d9-31ed-4e66-9696-7e1d35e2effd
< x-amz-apigw-id: LWGCREruoAMFgNA=
< X-Amzn-Trace-Id: Root=1-5e9f1d41-32c78080eb575700023c7c80;Sampled=0
< X-Cache: Miss from cloudfront
< Via: 1.1 4c636d1acba4193747390c896124ffcc.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: CDG50-C1
< X-Amz-Cf-Id: 67d2EN4pvHch5GSzZS2yHWAiO6DDXECLfSLZ9J9QuAgM1N8iyHQkrg==
<

100 22 0 0 100 22 0 19 0:00:01 0:00:01 --:--:-- 19
* Connection #0 to host proxy.srvc.cvf left intact

1 answer

1 accepted

0 votes
Answer accepted
Tejas Shah April 21, 2020

Never mind. I found it. I had not quoted the issue ids within the array object

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events