Essentially, I want the yetus report to comment on the appropriate jira. I
have tried the effective command-line from curl with success, verifying
credentials. However, when running with cloudbees setup, debugging has
shown JIRA_ISSUE is empty. So the effective URL changes to as follows
(secrets hidden), both of which return successfully.

curl -X POST -H "Accept: application/json" -H "Content-Type:
application/json" -d '{"body" : "test jira rest api message"}' --location "
https://issues.apache.org/jira/rest/api/2/issue/TEZ-3891/comment"; -u
"user:secret"
echo $?
0

curl -X POST -H "Accept: application/json" -H "Content-Type:
application/json" -d '{"body" : "test jira rest api message"}' --location "
https://issues.apache.org/jira/rest/api/2/issue/comment"; -u "user:secret"
echo $?
0
Questions,
1) How does JIRA_ISSUE get extracted from PR? (branch-name, commit message,
PR title)
Issues: TEZ-3891
2) Is there any interest in a fix that would improve this silent failure
where JIRA is not determined?

Setup
Tez PR. https://github.com/apache/tez/pull/85
Yetus: rel/0.12.0
Jenkins ci build: derived from hadoop-multipbranch
debugging enabled for below build.
https://ci-hadoop.apache.org/view/Tez/job/tez-multibranch/view/change-requests/job/PR-85/17/console

Thanks,
Jon

Reply via email to