Jira Jenkins integration

[venkatakrishanan r]

Hi, 

Iam integrating Jira & Jenkins and have used Jira software Cloud and Jenkins on AWS VM

Followed the DOC : https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-oauth-authentication and test connection was successful 

openjdk version "1.8.0_302"

Jenkins 2.303.2

1, Configured JIRA Trigger Plugin 1.0.1 in Jenkins tried with 1.0.0 but no luck 

While doing the basic testing in jira job has not trigger in Jenkins, Jenkins  logs 

java.lang.IllegalAccessException: Processing this request relies on deprecated behavior that will be disallowed in future releases of Java. See https://jenkins.io/redirect/stapler-reflective-access/ for more information. Details: Class org.kohsuke.stapler.RequestImpl can not access a member of class com.ceilfors.jenkins.plugins.jiratrigger.JiraCommentTrigger with modifiers "private"

 Could any one guide me 

[Eko Budiharto]

hi,

I got the same error message "

Jul 11, 2024 9:01:47 AM WARNING org.kohsuke.stapler.RequestImpl injectSetters

java.lang.IllegalAccessException: Processing this request relies on deprecated behavior that will be disallowed in future releases of Java. See https://jenkins.io/redirect/stapler-reflective-access/ for more information. Details: class org.kohsuke.stapler.RequestImpl cannot access a member of class com.ceilfors.jenkins.plugins.jiratrigger.JiraTrigger with modifiers "private"

"

I am using

-. JIRA DC on prem -> 9.17.0

-. JENKINS on prem -> 2.452.2

-. JDK 17.

[Eko Budiharto]

@Mark Rekveld - Marvelutionbro,

I have a question.

based on the article in this URL -> https://www.jenkins.io/doc/developer/handling-requests/deprecated-reflective-access/

the article:

Before Jenkins 2.272 Stapler would access all fields ignoring visibility restrictions.

Stapler now tries to access a field first and only if it gets access denied then will it force access via setAccessible(true).

This behavior is not recommended anymore, and will trigger IllegalReflectiveAccess warnings when running Jenkins on Java 11 or newer.

If you see a warning message about this then you should report an issue to the respective plugin.

Dec 15, 2020 9:22:33 PM org.kohsuke.stapler.lang.FieldRef$1 get
WARNING: java.lang.IllegalAccessException: Processing this request relies on deprecated behavior 

after comparing the jenkins version I use and the version mentioned in this article, the condition matched to give me the problem.

and 2nd condition, my JDK is newer than 11 also.

what should I do to solve the problem?

[Mark Rekveld - Marvelution]

Hi @Eko Budiharto 

Looking at the error in detail it seems this is related to the jira-trigger.

I would reach out to that team but it looks like the plugin is in need of adoption as the current developer can no longer maintain the plugin.

So if they cannot help, either at all or in a timely manner, then I would advice to move await from that plugin and start looking into alternatives.

Cheers,
Mark

[Eko Budiharto]

@Mark Rekveld - Marvelutionbro,

while waiting for any response from the plugin developer team, I am thinking to find another alternative. I found 2, a JIRA automation or "manage rule" in "JENKINS INTEGRATION" in JIRA.

When I search a guide to send a trigger to jenkins to start a build, so far I have no luck. The only automation between jira and jenkins is only "

If a build fails in Jenkins, then add a comment to the Jira issue and send a Slack message to the team channel."

URL : https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/1357170

You or other members in this community might can recommend a few alternative options available to send a trigger to jenkins to start a build in jenkins and/or a guide using automation for what I need and/or to use "manage rule" in "JENKINS INTEGRATION".

Thank you very much

[Mark Rekveld - Marvelution]

Hi @Eko Budiharto 

Yeah finding a plugin that works and is well maintained can be a challenge. Especially if you are looking to multiple features, they usually end up in multiple plugins that each require their own configuration.

The Jenkins Integration for Jira app aims to bundle features when it comes to integrating with Jira. It can trigger builds from Jira using a manual issue action or a workflow post function, provides automation rules for actions in Jira based on Jenkins results and provides an improved build to issue index to show how data in Jenkins relates to Jira and visa versa.

Disclaimer, I'm the developer of the app.

As far as I'm aware there is no single app/plugin that can perform this same level of integration. You can take a look at this page and the docs of the app for more details or schedule a demo.

[Anil Sharma]

hey @venkatakrishanan r  have you got any success on the above?

For me, alongwith the above in logs, i m getting below but could not get any clue

Caused by: java.lang.IllegalArgumentException: Text must not be null or empty
at groovy.json.JsonSlurper.parseText(JsonSlurper.java:203)
at groovy.json.JsonSlurper$parseText.call(Unknown Source)
at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:56)
at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source)
at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51)

[Muthu Kumaran Kamaraj]

Hi @Anil Sharma . We were using this with onprem jira and was working fine. However, See the same error as above when using the cloud SAAS JIRA. Were you able to make it work ?

Apr 17, 2024 5:30:57 PM WARNING org.eclipse.jetty.server.handler.ContextHandler$Context log
Error while serving https://jenkinsurl/jira-trigger-webhook-receiver/
java.lang.IllegalArgumentException: Text must not be null or empty
at groovy.json.JsonSlurper.parseText(JsonSlurper.java:203)
at groovy.json.JsonSlurper$parseText.call(Unknown Source)
at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:56)
at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source)
at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51)
at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:398)

[Anil Sharma]

the cloud version seems does not support this. We have left this task for good as of now .

[Mark Rekveld - Marvelution]

@Anil Sharma @Muthu Kumaran Kamaraj The Jenkins Integration for Jira app supports both Jira Data Center and Jira Cloud and can trigger builds in Jenkins from Jira using a manual issue action or a workflow post function.

It can also include issue field as build parameters.

Disclaimer, I'm the developer of the app.

[Muthu Kumaran Kamaraj]

Hi @Mark Rekveld . I tried this but unfortunately looks like the jenkins plugin doesnt support our current version of jenkins 2.332.3

Warning: This plugin is built for Jenkins 2.361.4 or newer. Jenkins will refuse to load this plugin if installed.

[Mark Rekveld - Marvelution]

Hi @Muthu Kumaran Kamaraj 

I just checked if I can simple add support for 2.332.3, but it doesn't seem to be simple version switch, and also requires code updates.

Do you have any plans to update your Jenkins instance to a newer version? 2.332 was released back in January of 2022.

[Eko Budiharto]

hi @Muthu Kumaran Kamaraj how can I contact you? I would like to ask how you set jira webhook on JIRA on prem working.

[Muthu Kumaran Kamaraj]

Hi @Eko Budiharto  It should be under system -> settings-> webhook. Can send me mail to muthu86.eee@gmail.com in case of queries not addressed here. 

[Muthu Kumaran Kamaraj]

@Mark Rekveld - Marvelution  Thanks. I have found another alternate to integrate jira SAAS with our jenkins with REST API's and all good for now.

Thanks for your suggestions.

[Eko Budiharto]

hi @Muthu Kumaran Kamaraj

I am sending an email to you.

[Mark Rekveld - Marvelution]

Sure thing @Muthu Kumaran Kamaraj Just in case it doesn't work out in the future, I have released support for Jenkins 2.222.4 in the previous gen Jenkins plugin required by the Jenkins Integration for Jira app.

You can get it from the release notes version 4.1.0.