[JIRA] (JENKINS-60113) IssueFieldUpdateStep wrong fieldValue type
Title: Message Title Radek Antoniuk updated JENKINS-60113 Jenkins / JENKINS-60113 IssueFieldUpdateStep wrong fieldValue type Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202959.1573238032000.1385.1585330800348%40Atlassian.JIRA.
[JIRA] (JENKINS-60113) IssueFieldUpdateStep wrong fieldValue type
Title: Message Title Radek Antoniuk updated JENKINS-60113 Jenkins / JENKINS-60113 IssueFieldUpdateStep wrong fieldValue type Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202959.1573238032000.1387.1585330800376%40Atlassian.JIRA.
[JIRA] (JENKINS-4439) Matrix builds jira comments are overly numerous
Title: Message Title Radek Antoniuk updated JENKINS-4439 This is really old, I'm just going to close it down as I don't expect anyone is running Jira 3.x nowadays. Jenkins / JENKINS-4439 Matrix builds jira comments are overly numerous Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Radek Antoniuk updated JENKINS-44989 Fixed long time ago in v. 2.5.2: https://github.com/jenkinsci/jira-plugin/pull/142 Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussi
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Radek Antoniuk Labels: jira-plugin-2.5.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183074.1497951893000.1373.1585330321554%40Atlassian.JIRA.
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Radek Antoniuk updated JENKINS-44989 Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183074.1497951893000.1375.1585330321609%40Atlassian.JIRA.
[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder
Title: Message Title Radek Antoniuk updated JENKINS-54108 Jenkins / JENKINS-54108 "JIRA: Progress issues by workflow action" fails when job is located within a folder Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194733.1539712134000.1358.1585329840775%40Atlassian.JIRA.
[JIRA] (JENKINS-54108) "JIRA: Progress issues by workflow action" fails when job is located within a folder
Title: Message Title Radek Antoniuk updated JENKINS-54108 I have just tested this scenario with current 2.222.1 and 3.0.14, looks like it works for me. If you still have an issue, please open a new ticket and try to attach a stacktrace (in DEBUG logging if needed) Jenkins / JENKINS-54108 "JIRA: Progress issues by workflow action" fails when job is located within a folder Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Radek Antoniuk commented on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level Since JENKINS-44524 this is configurable on the Folder level, which I think serves the purpose of security and transparency on who has access to what. Therefore I propose to close this and use folder configuration instead. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167054.1450212239000.1336.1585329120353%40Atlassian.JIRA.
[JIRA] (JENKINS-61689) java.lang.NullPointerException when configuring JIRA site in Folder level
Title: Message Title Radek Antoniuk commented on JENKINS-61689 Re: java.lang.NullPointerException when configuring JIRA site in Folder level I have just tested this using my Jira Cloud instance and a Docker Jenkins LTS 2.222.1 and current Jenkins Jira plugin 3.1.14 - all works fine for me. Try using a docker instance for troubleshooting to check if it works with your Jira instance - see https://github.com/jenkinsci/docker for help. If it still doesn't work for you with 3.0.14, please post new stacktrace. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205512.158519371.1333.1585328520154%40Atlassian.JIRA.
[JIRA] (JENKINS-60749) Authenticate using OAuth in JIRA plugin
Title: Message Title Radek Antoniuk commented on JENKINS-60749 Re: Authenticate using OAuth in JIRA plugin This is a really good idea. If you'd like to contribute, I think the below links could be a nice start for implementing this: https://wiki.jenkins.io/display/JENKINS/OAuth+Credentials https://github.com/jenkinsci/google-oauth-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204007.1578920189000.2596.1583695200179%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Radek Antoniuk commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Josh Brozen please follow the discussion in the Pull Request, as soon as it will be stable it will get merged and released Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.5534.1583348400638%40Atlassian.JIRA.
[JIRA] (JENKINS-61311) JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist
Title: Message Title Radek Antoniuk commented on JENKINS-61311 Re: JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist I have closed this as duplicate, please track the other ticket. The release will be done as soon as the related PRs are reviewed and merged. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204894.1583252702000.4760.1583321880180%40Atlassian.JIRA.
[JIRA] (JENKINS-61311) JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist
Title: Message Title Radek Antoniuk closed an issue as Fixed Jenkins / JENKINS-61311 JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204894.1583252702000.4756.1583321820404%40Atlassian.JIRA.
[JIRA] (JENKINS-61098) java.util.concurrent.ExecutionException when fetching user
Title: Message Title Radek Antoniuk updated JENKINS-61098 Jenkins / JENKINS-61098 java.util.concurrent.ExecutionException when fetching user Change By: Radek Antoniuk Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204594.1581693909000.1935.1583068440359%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-60925 Re: Integration with JIRA Craig Rodrigues thanks for the suggestions! I have already updated for #2, For #1 it would be great if you could submit a PR with new screenshots! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.2328.1582121880709%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk resolved as Incomplete I mentioned the guide already above that is documented on Jira Cloud section of https://plugins.jenkins.io/jira - follow this https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/ Jenkins / JENKINS-60925 Integration with JIRA Change By: Radek Antoniuk Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop rece
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-60925 Re: Integration with JIRA I'm referring to this, I don't know what dashboard do you mean.. Atlassian JIRA Cloud, it's not possible to create a user without an email, so you need to create API token. Then create a global Jenkins credential, where you put Atlassian ID email as username and API token as password. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.9759.1580568720051%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-60925 Re: Integration with JIRA I'm referring to this, I don't know what dashboard do you mean.. Atlassian JIRA Cloud, it's not possible to create a user without an email, so you need to create API token. Then create a global Jenkins credential, where you put Atlassian ID email as username and API token as password. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.9757.1580568670202%40Atlassian.JIRA.
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title Radek Antoniuk closed an issue as Incomplete Closing with timeout from the reporter. Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Change By: Radek Antoniuk Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegr
[JIRA] (JENKINS-53070) Jira-Plugin ignored no_proxy settings
Title: Message Title Radek Antoniuk resolved as Duplicate I believe it was was fixed in JENKINS-51164. Jenkins / JENKINS-53070 Jira-Plugin ignored no_proxy settings Change By: Radek Antoniuk Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.googl
[JIRA] (JENKINS-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-60930 jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Change By: Radek Antoniuk Labels: jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204327.1580464056000.9735.1580562060492%40Atlassian.JIRA.
[JIRA] (JENKINS-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Radek Antoniuk resolved as Duplicate Jenkins / JENKINS-60930 jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Change By: Radek Antoniuk Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204327.1580464056000.9732.1580562060422%40Atlassian.JIRA.
[JIRA] (JENKINS-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-60930 jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Change By: Radek Antoniuk Component/s: jira-issue-updater-plugin Component/s: jira-plugin Component/s: jiratestresultreporter-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204327.1580464056000.9729.1580562000246%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-60925 Re: Integration with JIRA Did you try following the steps described in Jira Cloud section of https://plugins.jenkins.io/jira ? Also take a look at official Atlassian plugin for integration between JIRA Cloud version and Jenkins: https://confluence.atlassian.com/adminjiracloud/integrate-jira-software-cloud-with-jenkins-972355471.html Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.9485.1580479020779%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-60925 Integration with JIRA Change By: Radek Antoniuk Priority: Blocker Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204322.158041457.9487.1580479020811%40Atlassian.JIRA.
[JIRA] (JENKINS-59916) SSRF on https://issues.jenkins-ci.org/
Title: Message Title Radek Antoniuk commented on JENKINS-59916 Re: SSRF on https://issues.jenkins-ci.org/ This is caused by a security vulnerability in Atlassian JIRA, not Jenkins Jira plugin that is only a consumer of Jira API, correct? This issue tracker for issues in Jenkins and/or Jenkins plugins only. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202715.1571915638000.4165.1572346800237%40Atlassian.JIRA.
[JIRA] (JENKINS-59921) How to update the status of an Jira issue from Jenkins piepline
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-59921 How to update the status of an Jira issue from Jenkins piepline Change By: Radek Antoniuk Component/s: jira-issue-updater-plugin Component/s: jira-trigger-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202720.1571926465000.4162.1572346440670%40Atlassian.JIRA.
[JIRA] (JENKINS-59921) How to update the status of an Jira issue from Jenkins piepline
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-59921 How to update the status of an Jira issue from Jenkins piepline Change By: Radek Antoniuk Labels: jenkins jira jira-plugin-2.4 pipeline plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202720.1571926465000.4159.1572346440629%40Atlassian.JIRA.
[JIRA] (JENKINS-59921) How to update the status of an Jira issue from Jenkins piepline
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-59921 How to update the status of an Jira issue from Jenkins piepline Change By: Radek Antoniuk Component/s: jira-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202720.1571926465000.4156.1572346440578%40Atlassian.JIRA.
[JIRA] (JENKINS-58911) Jira Plugin does not create new version in existing project
Title: Message Title Radek Antoniuk commented on JENKINS-58911 Re: Jira Plugin does not create new version in existing project Oh, I just noticed you are on Jira (Server) 5.2.10. Indeed, Jira 5.2.10 doesn't know the startDate field that the current version of Jenkins Jira plugin is using. https://docs.atlassian.com/software/jira/docs/api/5.2.10/index.html?com/atlassian/jira/rest/v2/issue/version/VersionBean.html https://docs.atlassian.com/software/jira/docs/api/7.3.2/com/atlassian/jira/rest/v2/issue/version/VersionBean.html We need to think how we can achieve backward compatibility with older Jira versions for cases like this, for now I guess you can only try using an older version of Jenkins Jira plugin or consider upgrading your Jira instance... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201251.1565711807000.4469.1570700400327%40Atlassian.JIRA.
[JIRA] (JENKINS-58628) jira-plugin not working from pipeline job: jiraIssueSelector doesn't find any issues
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-58628 jira-plugin not working from pipeline job: jiraIssueSelector doesn't find any issues Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200796.1563944957000.4454.1570699442748%40Atlassian.JIRA.
[JIRA] (JENKINS-58911) Jira Plugin does not create new version in existing project
Title: Message Title Radek Antoniuk commented on JENKINS-58911 Re: Jira Plugin does not create new version in existing project It seems that the API is now not accepting startDate field? What Jira type (Server or Cloud) and version are you using? Also, you should remove quotes from your version string, as you can see in the log they are double-quoted. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201251.1565711807000.4451.1570699380141%40Atlassian.JIRA.
[JIRA] (JENKINS-58714) Cannot save System Settings or update Jobs with latest JIRA Plugin versions
Title: Message Title Radek Antoniuk commented on JENKINS-58714 Re: Cannot save System Settings or update Jobs with latest JIRA Plugin versions Can you check with the current version, as this might be related to JENKINS-57899? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201006.1564423788000..1570699080818%40Atlassian.JIRA.
[JIRA] (JENKINS-59003) JENKINS and JIRA integration
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-59003 JENKINS and JIRA integration Change By: Radek Antoniuk Component/s: jira-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201355.1566272905000.4447.1570699141137%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Radek Antoniuk edited a comment on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile OK, I debugged it a little and I think I know what the problem is: even though I modified the ssh-credentials plugin to save with a newline, it still didn't work for me. It turns out that the ssh-agent plugin that writes the private key to the file, strips it out of the newline. Then... ssh-add asks for a password. When I add a newline, it adds it to the agent fine. The question is now, what is stripping this private key newline ... I'll continue to debug but any hints appreciated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189200.1521076967000.5321.1568735280276%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Radek Antoniuk commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile OK, I debugged it a little and I think I know what the problem is: even though I modified the ssh-credentials plugin to save with a newline, it still didn't work for me. It turns out that the ssh-agent plugin that writes the private key to the file, strips it out of the newline. Then... ssh-add asks for a password. When I add a newline, it adds it to the agent fine. The question is now, what is stripping this private key... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189200.1521076967000.5311.1568735220461%40Atlassian.JIRA.
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Radek Antoniuk commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Matt Sicker I am still experiencing this issue with ssh-credentials-plugin 1.17.2 / Jenkins 2.176.2, can this be re-opened? When I paste an SSH key without a password and without a newline after END OPENSSH PRIVATE KEY, I am getting this: [EnvInject] - Loading node environment variables. Building in workspace /opt/jenkins/workspace/tests/testssh [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-LjVbJNMcagCy/agent.130927 SSH_AGENT_PID=130929 [ssh-agent] Started. Running ssh-add (command line suppressed) Enter passphrase for /opt/jenkins/workspace/tests/testssh@tmp/private_key_4661922093191141579.key: ERROR: Failed to run ssh-add Finished: FAILURE When I update the key and put a newline, it works fine: Building in workspace /opt/jenkins/workspace/tests/testssh [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-LHBjsdVD6N7X/agent.130956 SSH_AGENT_PID=130958 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: /opt/jenkins/workspace/tests/testssh@tmp/private_key_1585458568929474760.key (SSH CI key) [ssh-agent] Using credentials jenkins (SSH key used for Tomcat restarts) [testssh] $ /bin/sh -xe /tmp/jenkins2172743275862346783.sh + hostname ci $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 130958 killed; [ssh-agent] Stopped. Finished: SUCCESS Add Comment
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title Radek Antoniuk closed an issue as Not A Defect It turns out that Tomcat didn't have enough write permissions to the /webapps folder to overwrite the previous WAR file. Jenkins / JENKINS-59068 SSL connection reset during deploy Change By: Radek Antoniuk Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201450.1566656778000.6.1566845520378%40Atlassian.JIRA.
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-59068
SSL connection reset during deploy
Change By:
Radek Antoniuk
Comment:
It gets even weirder, when I change the DSL to:{noformat} deploy adapters: [tomcat8(credentialsId: 'tomcat-dev', path: '/', url: "https://localhost:8080/manager/text" )], onFailure: false, war: 'target/ROOT.war' {noformat}it is trying to access wrong URL of the manager:{noformat}Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The Tomcat Manager responded "FAIL - Unknown command [/test/list] {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201450.1566656778000.10156.1566844200068%40Atlassian.JIRA.
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title Radek Antoniuk commented on JENKINS-59068 Re: SSL connection reset during deploy It gets even weirder, when I change the DSL to: deploy adapters: [tomcat8(credentialsId: 'tomcat-dev', path: '/', url: "https://localhost:8080/manager/text" )], onFailure: false, war: 'target/ROOT.war' it is trying to access wrong URL of the manager: Caused by: org.codehaus.cargo.container.tomcat.internal.TomcatManagerException: The Tomcat Manager responded "FAIL - Unknown command [/test/list] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201450.1566656778000.10155.1566844020226%40Atlassian.JIRA.
[JIRA] (JENKINS-59068) SSL connection reset during deploy
Title: Message Title
Radek Antoniuk created an issue
Jenkins / JENKINS-59068
SSL connection reset during deploy
Issue Type:
Bug
Assignee:
Unassigned
Components:
deploy-plugin
Created:
2019-08-24 14:26
Environment:
Jenkins ver. 2.176.2 deploy-plugin ver. 1.15
Priority:
Major
Reporter:
Radek Antoniuk
JENKINS-44810 added support for Jenkins Pipeline and I'm trying to deploy with the following declarative pipeline:
stage('Deploy') {
steps {
deploy adapters: [tomcat8(credentialsId: 'tomcat-dev', path: '/', url: "https://localhost:8080/manager/text" )], onFailure: false, war: 'target/ROOT.war'
}
}
and I'm getting:
16:15:27Deploying [/opt/jenkins/workspace/test/deploy/target/ROOT.war]
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Notified JIRA that a build has completed.
org.codehaus.cargo.container.ContainerException: Failed to deploy [/opt/jenkins/workspace/test/deploy/target/ROOT.war]
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.deploy(AbstractTomcatManagerDeployer.java:108)
at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:180)
at hudson.plugins.deploy.C
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title Radek Antoniuk commented on JENKINS-58554 Re: Workflow parse exception with new approach for unstable stages Got it, thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200704.1563458988000.15410.1563459600092%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title Radek Antoniuk commented on JENKINS-58554 Re: Workflow parse exception with new approach for unstable stages Devin Nusbaum any if I'm doing anything wrong in the Declarative definition? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200704.1563458988000.15404.1563459060050%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title
Radek Antoniuk created an issue
Jenkins / JENKINS-58554
Workflow parse exception with new approach for unstable stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-07-18 14:09
Environment:
Jenkins 2.176.1
Priority:
Minor
Reporter:
Radek Antoniuk
I am following https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/ blogpost to use the new try/catch approach:
stages {
stage ('Tests: EN'){
steps{
try {
sh 'HOME=$(pwd) bundle && HOME=$(pwd) LOCALE=en BROWSER=chrome-headless-nogpu cucumber --format json --out reports/en.json'
}
catch (ex) {
unstable('Tests failed!')
}
}
}
for marking the results unstable but I'm getting:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 21: Expected a step @ line 21, column 13.
try {
^
WorkflowScript: 32: Expected a step @ line 32, column 13.
try{
^
WorkflowScript: 43: Expected a step @ line 43, column 13.
try{
^
3 errors
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at org.codehaus.groo
[JIRA] (JENKINS-58519) Add OWASP to BlueOcean view
Title: Message Title Radek Antoniuk created an issue Jenkins / JENKINS-58519 Add OWASP to BlueOcean view Issue Type: New Feature Assignee: Unassigned Attachments: Screenshot 2019-07-16 16.59.57.png Components: blueocean-plugin, dependency-check-jenkins-plugin Created: 2019-07-16 15:05 Priority: Minor Reporter: Radek Antoniuk JENKINS-37437 added support for OWASP dependency checker that shows a neat UI report: It would be great to have this colorful bar visible in a blueocean view, below the branch info details and/or in the Tests tab. Add Comment
[JIRA] (JENKINS-55348) Display Pull Request Name instead of ID in the UI
Title: Message Title Radek Antoniuk commented on JENKINS-55348 Re: Display Pull Request Name instead of ID in the UI The Pull Request name can be really long and although less UX friendly, it's more UI friendly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196444.1545944269000.11995.1561751460229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Radek Antoniuk commented on JENKINS-57695 Re: Jira issue not created when jenkins build failed I can confirm that I am able to replicate this on my test environment. Comparing the changes in the last releases, I think this is caused by changes introduced since 3.0.5. I'll try to take a look at this next week, if you have some time to investigate, please check v. 3.0.5 if it was working for you correctly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.20630.1559648220456%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-57695
Jira issue not created when jenkins build failed
Change By:
Radek Antoniuk
I have setup the 3. 6. 0 .6 version of Jira plugin for jenkins with my jenkins instance. I am having issue with "Create jira issue" upon job failure. Below is the error i am getting (from Console Output) {noformat} Build step 'Execute shell' marked build as failure ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:413) at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:202) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:357) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:157) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'JIRA: Create issue' marked build as failure Finished: FAILURE{noformat} Need urgent help to fixing it. RegardsSachin Gahlawat
Add Comment
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57695 Jira issue not created when jenkins build failed Change By: Radek Antoniuk Labels: confirmed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.20614.1559647020571%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title Radek Antoniuk commented on JENKINS-53780 Re: jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Can you check if this still occurs with the current plugin version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194290.1537948123000.17726.1559320440073%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing by timeout, feel free to reopen if you validated your credentials with curl and you believe that's a bug. https://issues.jenkins-ci.org/secure/AddComment!default.jspa?id=198519 Jenkins / JENKINS-56577 Unable to add Jira Site Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198192.1552639896000.17724.1559320320412%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56677) Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing by timeout, feel free to reopen if you validated your credentials with curl and you believe that's a bug. https://issues.jenkins-ci.org/secure/AddComment!default.jspa?id=198519 Jenkins / JENKINS-56677 Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198314.1553248627000.17722.1559320320304%40Atlassian.JIRA. For more options, visit https://groups.google.
[JIRA] (JENKINS-56857) Unable to validate JIRA site
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Closing by timeout, feel free to reopen if you validated your credentials with curl and you believe that's a bug. Jenkins / JENKINS-56857 Unable to validate JIRA site Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198519.1554240962000.17720.1559320260448%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-54486 Not created JIRA issue after build failed Change By: Radek Antoniuk Labels: build jenkins jira plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17688.1559319840758%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk stopped work on JENKINS-54486 Change By: Radek Antoniuk Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17681.1559319840629%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk assigned an issue to Unassigned Jenkins / JENKINS-54486 Not created JIRA issue after build failed Change By: Radek Antoniuk Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17685.1559319840703%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk commented on JENKINS-54486 Re: Not created JIRA issue after build failed I don't think so as here we don't have any NPE. Interestingly the reporter mentions two plugins for JIRA, one is the open source one (v. 3.0.5) and the other one is (I'm assuming) the Marvellution plugin. So as a first shot, I'd propose disabling one of the plugins, configuring the other one and checking if you get the correct results as they might interfere with each other. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195256.1541502017000.17666.1559317800176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-57695
Jira issue not created when jenkins build failed
Change By:
Radek Antoniuk
I have setup the 3.6.0 version of Jira plugin for jenkins with my jenkins instance. I am having issue with "Create jira issue" upon job failure. Below is the error i am getting (from Console Output) {noformat} Build step 'Execute shell' marked build as failureERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:413) at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:202) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:357) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:157) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'JIRA: Create issue' marked build as failureFinished: FAILURE {noformat} Need urgent help to fixing it. RegardsSachin Gahlawat
Add Comment
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Radek Antoniuk commented on JENKINS-57695 Re: Jira issue not created when jenkins build failed 3.0.7 for the jira-plugin - please update the jira-plugin to the current version from the Update Center Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.13554.1559042460186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Radek Antoniuk commented on JENKINS-57695 Re: Jira issue not created when jenkins build failed Does the validate button in JIRA site definition in global configuration validates the connection correctly? Can you try version 3.0.7 of the plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.13523.1559038680110%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57695 Jira issue not created when jenkins build failed Change By: Radek Antoniuk Environment: Jenkins ver. 2.150.1, Centos OS jira-plugin 3.0.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.13509.1559035980172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57695 Jira issue not created when jenkins build failed Change By: Radek Antoniuk Labels: exception jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.13427.1559035860771%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception I was able to re-produce the NPE on a plain Jenkins instance that had no JIRA site defined in the Global settings. Can you try the following: go to Global configuration and ensure connectivity to JIRA with the Validate button? (then Save configuration and re-run the build) if that doesn't help, can you try removing and re-adding the JIRA site? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.13026.1558999500154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57664 On Release of a Version recieve a Null Pointer exception Change By: Radek Antoniuk Environment: Jenkins version 2.164.3Jira Plugin version 3. 07 0.7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11955.1558798260111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk edited a comment on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception Uhm, I'm confused, you're mentioning Slack now. Did the problem occur because of Slack plugin? Or do you mean that after re-saving the job configuration it just started working?If the latter, are you able to dig out the full stacktrace still? It might help figuring out why the jobs needed to be re-saved after plugin update. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11953.1558798080082%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception Uhm, I'm confused, you're mentioning Slack now. Did the problem occur because of Slack plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11951.1558798020080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Radek Antoniuk commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception Can you attach full stacktrace from Jenkins logs? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.11928.1558794420105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34774) ClosedChannelException in log (excessive)
Title: Message Title Radek Antoniuk closed an issue as Fixed This should be fixed in jira-plugin 2.5.2. If not, please reopen with current logs from current Jenkins and jira-plugin, thanks! Jenkins / JENKINS-34774 ClosedChannelException in log (excessive) Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170424.1463073889000.9828.1558600980894%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) U\nable to find valid certification path
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57619 U\nable to find valid certification path Change By: Radek Antoniuk Summary: jenkins -jira integration U\nable to find valid certification path Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199547.1558546618000.9824.1558600800242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) Unable to find valid certification path
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-57619 Unable to find valid certification path Change By: Radek Antoniuk Summary: U\nable Unable to find valid certification path Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199547.1558546618000.9826.1558600800266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) jenkins -jira integration
Title: Message Title Radek Antoniuk edited a comment on JENKINS-57619 Re: jenkins -jira integration What certificate is used on the JIRA side? Can you connect directly to JIRA with curl via the command-line? Also, please add details in the issue about JIRA and jenkins plugin versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199547.1558546618000.9822.1558600740122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57619) jenkins -jira integration
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-57619
jenkins -jira integration
Change By:
Radek Antoniuk
{noformat} sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source) at java.security.cert.CertPathBuilder.build(Unknown Source)Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(Unknown Source) at sun.security.validator.PKIXValidator.engineValidate(Unknown Source) at sun.security.validator.Validator.validate(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Alerts.getSSLException(Unknown Source) at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.Handshaker.fatalSE(Unknown Source) at sun.security.ssl.ClientHandshaker.serverCertificate(Unknown Source) at sun.security.ssl.ClientHandshaker.processMessage(Unknown Source) at sun.security.ssl.Handshaker.processLoop(Unknown Source) at sun.security.ssl.Handshaker$1.run(Unknown Source) at sun.security.ssl.Handshaker$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.security.ssl.Handshaker$DelegatedTask.run(Unknown Source) at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask(SSLIOSession.java:284) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:352)Caused: javax.net.ssl.SSLHandshakeException: General SSLEngine problem at sun.security.ssl.Handshaker.checkThrown(Unknown Source) at sun.security.ssl.SSLEngineImpl.checkTaskThrown(Unknown Source) at sun.security.ssl.SSLEngineImpl.writeAppRecord(Unknown Source) at sun.security.ssl.SSLEngineImpl.wrap(Unknown Source) at javax.net.ssl.SSLEngine.wrap(Unknown Source) at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap(SSLIOSession.java:266) at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSLIOSession.java:306) at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady(SSLIOSession.java:508) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:120) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.Abstra
[JIRA] (JENKINS-57619) jenkins -jira integration
Title: Message Title Radek Antoniuk commented on JENKINS-57619 Re: jenkins -jira integration What certificate is used on the JIRA side? Can you connect directly to JIRA with curl via the command-line? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199547.1558546618000.9818.1558600620200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54469) Unable to set Thread Executor Size when configuring Jira Plugin
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-54469 Unable to set Thread Executor Size when configuring Jira Plugin Change By: Radek Antoniuk Labels: jira-plugin-3.0.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195234.1541437984000.9.1557417120447%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-54116 Jenkins Jira Plugin - Unable to add version Change By: Radek Antoniuk Labels: jira- plugin -3.0.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194742.1539757445000.22237.1557417180412%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Radek Antoniuk closed an issue as Fixed Fixed in 3.0.5 Jenkins / JENKINS-54116 Jenkins Jira Plugin - Unable to add version Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194742.1539757445000.22235.1557417180388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54469) Unable to set Thread Executor Size when configuring Jira Plugin
Title: Message Title Radek Antoniuk closed an issue as Fixed I just checked this with 3.0.7 and all works fine for me, feel free to reopen if this still applies. Jenkins / JENKINS-54469 Unable to set Thread Executor Size when configuring Jira Plugin Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195234.1541437984000.7.1557417120420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Radek Antoniuk commented on JENKINS-55982 Re: JIRA Plugin does not respect proxy in some requests Can you check the current version of plugin (3.0.7) and make sure you define the proxy in Manage Jenkins > Manage Plugins > Advanced ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197394.1549394874000.4.1557416760104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-56417 Jenkins cannot release Jira version 'No content to map to Object due to end of input' Change By: Radek Antoniuk Environment: Jenkins 2.166 withjira-plugin version 306 and Jira version 3.0.6JIRA 8.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198008.1551797348000.0.1557416520163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk edited a comment on JENKINS-56417 Re: Jenkins cannot release Jira version 'No content to map to Object due to end of input' Since you mentioned a change in your configuration (I'm assuming on the JIRA side), can you make sure all /rest/ requests are passed correctly to JIRA? (Try looking up what flows between Jenkins and JIRA with tcpdump/tcpick or wireshark). Also, is this JIRA Server or Cloud? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198008.1551797348000.2.1557416520185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk commented on JENKINS-56417 Re: Jenkins cannot release Jira version 'No content to map to Object due to end of input' Since you mentioned a change in your configuration (I'm assuming on the JIRA side), can you make sure all /rest/ requests are passed correctly to JIRA? (Try looking up what flows between Jenkins and JIRA with tcpdump/tcpick or wireshark). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198008.1551797348000.22218.1557416460094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56857) Unable to add Jira site in jenkins
Title: Message Title Radek Antoniuk commented on JENKINS-56857 Re: Unable to add Jira site in jenkins That usually means that there is a problem with accessing your JIRA instance (yeah, I know, the info is not too informative now). Are you integrating with standalone JIRA or Cloud? Can you try checking a curl request from your Jenkins host if it correctly returns JSON with the credentials you provided? See authentication info. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198519.1554240962000.22198.1557416040413%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56577) Unable to add Jira Site
Title: Message Title Radek Antoniuk commented on JENKINS-56577 Re: Unable to add Jira Site Also can you try current Jenkins(2.176) and Jira plugin version (3.0.7) on a test instance? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198192.1552639896000.22214.1557416340096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56857) Unable to validate JIRA site
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-56857
Unable to validate JIRA site
Change By:
Radek Antoniuk
After adding the Jira URL, validate settings shows below error: {code:java} java.lang.NullPointerException at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:1179) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.d
[JIRA] (JENKINS-56677) Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Title: Message Title Radek Antoniuk commented on JENKINS-56677 Re: Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog hudson.plugins.jira.JiraSite.createSession(JiraSite.java:295) This means that probably Jenkins has trouble connecting to your JIRA instance. Does JIRA integration work fine in other places in Jenkins? Can you try VALIDATE button in Jenkins JIRA site settings? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198314.1553248627000.22212.1557416220084%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56677) Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-56677
Jenkins build failed with java.lang.NullPointerException caused:java.io.IOException: Failed to parse changelog
Change By:
Radek Antoniuk
{code: java }java .lang.NullPointerException at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:295) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:278) at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:38) at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)Caused: java.io.IOException: Failed to parse changelog at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from
[JIRA] (JENKINS-56857) Unable to validate JIRA site
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-56857 Unable to validate JIRA site Change By: Radek Antoniuk Summary: Unable to add Jira validate JIRA site in jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198519.1554240962000.22200.1557416040439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title Radek Antoniuk commented on JENKINS-57004 Re: Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED That's interesting, can you try upgrading to 3.0.7 and restarting Jenkins instance and see if the problem persists? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198705.1555286407000.22184.1557415800101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33101) JIRA Jenkins integration
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce The stacktrace mentions "com.marvelution.jenkins.plugins.jira.filter" which is a Marvelution plugin, not the Open Source Jenkins JIRA plugin. Please contact Marvelution support. Jenkins / JENKINS-33101 JIRA Jenkins integration Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168468.1456230079000.22180.1557415440271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57239) Error while integrating jenkins and jira
Title: Message Title Radek Antoniuk commented on JENKINS-57239 Re: Error while integrating jenkins and jira The stacktrace you posted doesn't even mention the plugin, it doesn't even mention hudson/jenkins, but you can see java.lang.ClassNotFoundException. Can you add more info? Jenkins and plugin version? when are you executing getting this stracktrace? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199002.1556612051000.22176.1557415080492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57239) Error while integrating jenkins and jira
Title: Message Title
Radek Antoniuk updated an issue
Jenkins / JENKINS-57239
Error while integrating jenkins and jira
Change By:
Radek Antoniuk
{code: java }java .lang.ClassCastException: Cannot cast com.att.aft.dme2.internal.jersey.core.impl.provider.header.LocaleProvider to com.sun.jersey.spi.HeaderDelegateProvider at java.lang.Class.cast(Class.java:3369) at com.sun.jersey.spi.service.ServiceFinder$LazyObjectIterator.hasNext(ServiceFinder.java:833) at com.sun.jersey.core.spi.factory.AbstractRuntimeDelegate.(AbstractRuntimeDelegate.java:76) at com.sun.ws.rs.ext.RuntimeDelegateImpl.(RuntimeDelegateImpl.java:56) at sun.reflect.GeneratedConstructorAccessor303.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at java.lang.Class.newInstance(Class.java:442) at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:65)Caused: java.lang.ClassNotFoundException: Provider com.sun.ws.rs.ext.RuntimeDelegateImpl could not be instantiated at javax.ws.rs.ext.FactoryFinder.newInstance(FactoryFinder.java:69) at javax.ws.rs.ext.FactoryFinder.find(FactoryFinder.java:155) at javax.ws.rs.ext.RuntimeDelegate.findDelegate(RuntimeDelegate.java:105) {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
Yo
[JIRA] (JENKINS-56951) JIRA plugin config incorrectly mixed with properties section
Title: Message Title Radek Antoniuk closed an issue as Fixed Jenkins / JENKINS-56951 JIRA plugin config incorrectly mixed with properties section Change By: Radek Antoniuk Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Radek Antoniuk updated JENKINS-52906 Jenkins / JENKINS-52906 jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33222) Concurrent builds are blocking with jira-plugin
Title: Message Title Radek Antoniuk updated JENKINS-33222 Jenkins / JENKINS-33222 Concurrent builds are blocking with jira-plugin Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-19195) Add description field to Release JIRA version action
Title: Message Title Radek Antoniuk updated JENKINS-19195 Jenkins / JENKINS-19195 Add description field to Release JIRA version action Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41690) JiraProjectProperty.setSites() doesn't set sites, it adds them (resulting in duplicate sites)
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-41690 JiraProjectProperty.setSites() doesn't set sites, it adds them (resulting in duplicate sites) Change By: Radek Antoniuk Labels: jira-plugin-2.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41690) JiraProjectProperty.setSites() doesn't set sites, it adds them (resulting in duplicate sites)
Title: Message Title Radek Antoniuk stopped work on JENKINS-41690 Change By: Radek Antoniuk Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51164) JIRA plugin doesn't honor proxy excludes
Title: Message Title Radek Antoniuk updated JENKINS-51164 Jenkins / JENKINS-51164 JIRA plugin doesn't honor proxy excludes Change By: Radek Antoniuk Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52667) JIRA link not detected if several trackers are configured
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-52667 JIRA link not detected if several trackers are configured Change By: Radek Antoniuk Labels: jira-plugin-3.0.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
