[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Usama Tariq https://github.com/jenkinsci/jira-trigger-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.201336.1566200967000.4879.1585804620284%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Wisen Tanasa closed an issue as Duplicate Thanks for all the details. Apologies, but apparently based on the error above, this is a duplicate of JENKINS-58987, closing this. Jenkins / JENKINS-61488 Jenkins Build not getting triggered even after receiving Jira Webhook Callback Change By: Wisen Tanasa Status: Open Closed Resolution: Duplicate 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
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Wisen Tanasa commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Amrut dengre That's great, at least you're not actually hitting network issue. Can you add back the "comment pattern", but keep the "JQL Filter"? Will it get the build triggered? I'm not quite sure why the "CODEBUILD" comment is not triggering the build, it should trigger it. On talking back to JIRA, this is required for JQL Filter to work, please see this section in the documentation: https://github.com/jenkinsci/jira-trigger-plugin#jenkins-global-configuration-one-time 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.205173.1584341702000.7620.1584349200515%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Wisen Tanasa commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback To troubleshoot: Can you try to remove the "JQL Filter" and see if that triggers the build? (Check if you have configured Jenkins to talk to JIRA) If a build is still not triggered, can you remove the "Comment pattern" and see if that triggers the build? 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.205173.1584341702000.7490.1584342061364%40Atlassian.JIRA.
[JIRA] (JENKINS-61488) Jenkins Build not getting triggered even after receiving Jira Webhook Callback
Title: Message Title Wisen Tanasa commented on JENKINS-61488 Re: Jenkins Build not getting triggered even after receiving Jira Webhook Callback Amrut dengre Thank you for raising this issue. To help the community navigate JIRA better, do kindly move your comments from JENKINS-58987 here too. 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.205173.1584341702000.7485.1584341940134%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Amrut dengre please raise another ticket in JIRA, it doesn't sound like you're facing the same issue with this issue here. 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.201336.1566200967000.7461.1584340860502%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title
Wisen Tanasa edited a comment on JENKINS-58987
Re: issue_updated trigger handler can't find "name" field in JSON
I've just reopened this issue as it's not fixed yet. I'm currently the maintainer of this plugin, and I genuinely struggle to maintain this as I no longer use Jenkins. So here's my current plan: * I'm happy to review, merge, and publish a PR if someone can make a working change. * If I'm involved in the fix, I need to justify my *personal time* (+I don't maintain this plugin for work+) that people are genuinely finding this plugin useful. I have set up an OpenCollective with $100 £75 /month fundraising goal: [https://opencollective.com/jira-trigger-plugin]. That's roughly $5 £3 for 20 25 backers, which is less than 1% of the current active installation (3400). If your business genuinely find this plugin helpful, consider contributing to the collective. It will help me get off my couch and help people out. ** Please get familiar with the open source model. Think of $5 £3 as you buying me a drink! Many of us are not paid to maintain this plugin and purely motivated because it was fun, it will help if you don't treat us like Jenkins support person. We're not part of CloudBees either. * As [~oleg_nenashev] has mentioned, I'm happy for this plugin to be adopted. I've marked this plugin in the home page that I'm looking for a co-maintainer last year, so that I can help on board you and get comfortable with the codebase. Please reach out to me if you're interested in this, even just slightly!These are how this issue must be tackled: * Long term fix: completely remove JRJC and apply the Postel's Law i.e. the plugin shouldn't break when JIRA changes, especially when it's not used internally within the plugin. * Med term fix: Upgrade JRJC. [~rodrigc] has kindly raised a PR [here in GitHub|https://github.com/jenkinsci/jira-trigger-plugin/pull/6]. However, it's hitting a build failure at the moment with {{NoClassDefFoundError}}. * Short term fix: fill in "name" variable with hardcoded value to satisfy the older version of JRJC.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Usama Tariq, Amrut dengre, Ashok T R, please read the comment that I've left above. It has taken a while for the OpenCollective to be set up, it's now live at: https://opencollective.com/jira-trigger-plugin. Hey Usama Tariq, I don't have the exact quote unfortunately, how much do you think this fix is worth to your business? That can be the guiding point to how much you want to contribute. The idea of contributing to OpenCollective is important as I'd like to emphasise that the contribution goes to the community (not me), hence people who are interested to become a maintainer in the future will be able to sustain their effort to keep this project healthy. I hope it makes sense. 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.201336.1566200967000.7377.1584307140259%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON I've just reopened this issue as it's not fixed yet. I'm currently the maintainer of this plugin, and I genuinely struggle to maintain this as I no longer use Jenkins. So here's my current plan: I'm happy to review, merge, and publish a PR if someone can make a working change. If I'm involved in the fix, I need to justify my personal time (I don't maintain this plugin for work) that people are genuinely finding this plugin useful. I have set up an OpenCollective with $100/month fundraising goal: https://opencollective.com/jira-trigger-plugin. That's roughly $5 for 20 backers, which is less than 1% of the current active installation (3400). If your business genuinely find this plugin helpful, consider contributing to the collective. It will help me get off my couch and help people out. Please get familiar with the open source model. Think of $5 as you buying me a drink! Many of us are not paid to maintain this plugin and purely motivated because it was fun, it will help if you don't treat us like Jenkins support person. We're not part of CloudBees either. As Oleg Nenashev has mentioned, I'm happy for this plugin to be adopted. I've marked this plugin in the home page that I'm looking for a co-maintainer last year, so that I can help on board you and get comfortable with the codebase. Please reach out to me if you're interested in this, even just slightly! These are how this issue must be tackled: Long term fix: completely remove JRJC and apply the Postel's Law i.e. the plugin shouldn't break when JIRA changes, especially when it's not used internally within the plugin. Med term fix: Upgrade JRJC. Craig Rodrigues has kindly raised a PR here in GitHub. However, it's hitting a build failure at the moment with NoClassDefFoundError. Short term fix: fill in "name" variable with hardcoded value to satisfy the older version of JRJC. Add Comment
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa updated JENKINS-58987 Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Wisen Tanasa Resolution: Duplicate Status: Fixed but Unreleased Reopened 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.201336.1566200967000.4914.1583909822033%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Wisen Tanasa closed an issue as Duplicate Jenkins / JENKINS-53794 jira-trigger-plugin fails to trigger job and throws error Change By: Wisen Tanasa Status: Reopened Closed Resolution: Duplicate 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.194307.1537972591000.4912.1583909822012%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa edited a comment on JENKINS-61184 Re: Jira Trigger Plugin Issue [~rlinux57] Thanks for raising this issue. This plug-in is open sourced, and is not maintained by the Jenkins team. I've closed this as a duplicate to JENKINS-58987 . In the mean time, feel free to submit a pull request to the project and I'm more than happy to merge it. 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.204728.1582314984000.4884.1583909761132%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Wisen Tanasa updated JENKINS-53794 Jenkins / JENKINS-53794 jira-trigger-plugin fails to trigger job and throws error Change By: Wisen Tanasa Resolution: Fixed Status: Fixed but Unreleased Reopened 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.194307.1537972591000.4886.1583909761164%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa commented on JENKINS-61184 Re: Jira Trigger Plugin Issue Usama Tariq Thanks for raising this issue. This plug-in is open sourced, and is not maintained by the Jenkins team. I've closed this as a duplicate. In the mean time, feel free to submit a pull request to the project and I'm more than happy to merge it. 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.204728.1582314984000.5604.1582576440123%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa closed an issue as Duplicate Jenkins / JENKINS-61184 Jira Trigger Plugin Issue Change By: Wisen Tanasa Status: Open Closed 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.204728.1582314984000.5595.1582576200229%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa assigned an issue to Unassigned Jenkins / JENKINS-61184 Jira Trigger Plugin Issue Change By: Wisen Tanasa Assignee: Dan Alvizu 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.204728.1582314984000.5593.1582576080279%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Wisen Tanasa commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Thank you for chasing it up with JRJC client Stefan Cordes. Would you be interested to file a PR? I saw in the JRJC PR that you've made a code change that will make jira-trigger-plugin back to work again. Thanks! 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.194307.1537972591000.5023.1582486860524%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 Wisen Tanasa commented on JENKINS-60930 Re: jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Thanks for raising this issue! I'm closing this one as it's duplicated with JENKINS-53794. 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.9709.1580546820136%40Atlassian.JIRA.
[JIRA] (JENKINS-59254) Jira not triggering builds on jenkins
Title: Message Title Wisen Tanasa commented on JENKINS-59254 Re: Jira not triggering builds on jenkins This might happen when the comment pattern you've set is not matched by the comment you've put in JIRA. Looking at the configuration, you've put a double quote, that might mean that you need to have double quote in JIRA as well. Try removing the double quote in JIRA, or make the comment pattern simpler. 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.201718.1567715124000.830.1568143320161%40Atlassian.JIRA.
[JIRA] (JENKINS-38797) Resolve Jira customfields from within the parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-38797 Re: Resolve Jira customfields from within the parameter mapping Vipul Madaan I'm not sure if your issue is related to this ticket, please do raise another ticket. 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.175199.1475779759000.821.1568142600247%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON That's ok. Is your job working now then I presume? 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.201336.1566200967000.3510.1567196700116%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Wisen Tanasa commented on JENKINS-58754 Re: JIRA-JENKINS Integration | JsonException Selva G The endpoint that you're trying to hit is not supposed to be hit manually, it'll be hit by JIRA automatically on issue change. If you observe that there's no job triggered, please follow the troubleshooting guide and see if you have a connectivity issue: https://github.com/jenkinsci/jira-trigger-plugin#troubleshooting 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.201057.1564657212000.3505.1567195500414%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Wisen Tanasa commented on JENKINS-58754 Re: JIRA-JENKINS Integration | JsonException Selva G That sounds quite different from what has been raised in this ticket. Regardless, that sounds like a connectivity issue. Please follow the troubleshooting guide and post back the result here. 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.201057.1564657212000.1564.1566972660212%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi Tomasz Kurcz. Apologies for your difficult project setup experience. I'm guessing that's because of the openjdk use. This project is tested with Oracle's JDK, not openjdk. That's for attempting to fix this. I've been trying to reproduce this issue to no avail. The issue_updated event's comment will not be parsed at all, so I still can't fully digest what's going on in your scenario. That said, there is a similar issue with a similar stack trace raised in StackOverflow. With the payload, I've managed to reproduce the same bug: JSONObject["name"] not found. org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser.parse(CommentJsonParser.java:37) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookCommentEventJsonParser.parse(WebhookCommentEventJsonParser.groovy:40) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:71) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookTest.Should fire comment created event when a comment is added in JIRA Cloud(JiraWebhookTest.groovy:136) 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
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Wisen Tanasa commented on JENKINS-58754 Re: JIRA-JENKINS Integration | JsonException We're not clear about what you're trying to achieve. Can you explain the problem that you're trying to solve? If you're having difficulty with the integration, please follow the troubleshooting guide and post back the result here: https://github.com/jenkinsci/jira-trigger-plugin#troubleshooting 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.201057.1564657212000.1041.1566933900156%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON I've just tested locally with your payload and it's not triggering the same stack trace too. The stack trace is also clearly showing that it's trying to parse comment events: ``` at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookCommentEventJsonParser.parse(WebhookCommentEventJsonParser.groovy:40) ``` Additionally, the URL of your JIRA doesn't seem to be JIRA Cloud. Atlassian hasn't deprecated the name field in JIRA Server. The issue-updated-event.json may contain comments, especially when you've left a comment in JIRA. JIRA will actually trigger issue-updated-event on comments too (I can't remember which version). Is it worth double checking if that's the only event you get? If it makes it easier, you can enable the FINE logging level to get all the webhook events printed out, by following this guide: https://github.com/jenkinsci/jira-trigger-plugin#troubleshooting 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.201336.1566200967000.8953.1566591240130%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Thanks for raising this issue Tomasz Kurcz. You're analysis looks correct to me. The exception stack trace shows the following stack: at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) Would you be able to attach the JSON data that you get for reproducibility? As this plug-in is relying on JRJC library, I can see that there is an active Pull Request that attempts to fix this issue. Unfortunately this PR is 5 months old as of today. Alternatively, we can inject a dummy name value to remove the parsing error. The value can be something like "User name attribute is not available, see https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/". This project is open source, would you be interested to make the code change? 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.201336.1566200967000.6442.1566330480221%40Atlassian.JIRA.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa closed an issue as Not A Defect Jenkins / JENKINS-58883 Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin Change By: Wisen Tanasa 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.201216.1565453675000.6431.1566328920228%40Atlassian.JIRA.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58883 Re: Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin It seems like your JIRA license has expired? I don't think it's related to this plug-in. Try to renew your JIRA license and see if the issue 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.201216.1565453675000.6429.1566328860090%40Atlassian.JIRA.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58883 Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin Change By: Wisen Tanasa Hi .I have installed the JIRA Plugins as "JIRA trigger plugins", " Jira issue updater", And " Jira integration for Jenkin" Few weeks earlier , While I was making any status change in the JIRA issue, it was triggering the build in Jenkin and parallely i could see the update in the "comment" in JIRA.but from few days , while having a status change of bug in JIRA , it does not allow to trigger the build in Jenkin and also there is no comment update in JIRA. but other options , like activity, user statistics , history get updated.during this execution i am facing licensing issue."TESTAA-1 test_jenkin - 2019-08-10 The license key is expired or invalid. Click here if you are Jira administrator. Digest generated on Aug 10 at 8:14 AMConfigure Powered by Email Notifications Digest add-on for Jira"Please help mei am using jenkin : 2.89.2Test JIRA server : 7.13.0RegardsAbhishek 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
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58883 Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin Change By: Wisen Tanasa Environment: Hi .I have installed the JIRA Plugins as "JIRA trigger plugins", " Jira issue updater", And " Jira integration for Jenkin" Few weeks earlier , While I was making any status change in the JIRA issue, it was triggering the build in Jenkin and parallely i could see the update in the "comment" in JIRA.but from few days , while having a status change of bug in JIRA , it does not allow to trigger the build in Jenkin and also there is no comment update in JIRA. but other options , like activity, user statistics , history get updated.during this execution i am facing licensing issue."TESTAA-1 test_jenkin - 2019-08-10 The license key is expired or invalid. Click here if you are Jira administrator. Digest generated on Aug 10 at 8:14 AMConfigure Powered by Email Notifications Digest add-on for Jira"Please help mei am using jenkin : 2.89.2Test JIRA server : 7.13.0RegardsAbhishek 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.201216.1565453675000.6423.1566328740513%40Atlassian.JIRA.
[JIRA] (JENKINS-59003) JENKINS and JIRA integration
Title: Message Title Wisen Tanasa assigned an issue to Wisen Tanasa Jenkins / JENKINS-59003 JENKINS and JIRA integration Change By: Wisen Tanasa Assignee: Kohsuke Kawaguchi Wisen Tanasa 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.201355.1566272905000.6419.1566328380159%40Atlassian.JIRA.
[JIRA] (JENKINS-59003) JENKINS and JIRA integration
Title: Message Title Wisen Tanasa commented on JENKINS-59003 Re: JENKINS and JIRA integration Hello, please follow this troubleshooting guideline and post the result back here: https://github.com/jenkinsci/jira-trigger-plugin#build-is-not-triggered 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.201355.1566272905000.6416.1566328320123%40Atlassian.JIRA.
[JIRA] (JENKINS-52742) jira-trigger-plugin not supported using jenkinsfile
Title: Message Title Wisen Tanasa commented on JENKINS-52742 Re: jira-trigger-plugin not supported using jenkinsfile Hi shagun jian, thanks for raising this issue. Unfortunately this is not supported at the moment. The project is open sourced, your contribution is welcomed to the plug-in to support this feature. 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.192635.153252705.14785.1563394800087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58276) Jira Cloud - Jenkins connectivity | Security measures
Title: Message Title Wisen Tanasa assigned an issue to sanoop raj p s Jenkins / JENKINS-58276 Jira Cloud - Jenkins connectivity | Security measures Change By: Wisen Tanasa Assignee: Wisen Tanasa sanoop raj p s 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.200340.1561969181000.457.1562133780326%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58276) Jira Cloud - Jenkins connectivity | Security measures
Title: Message Title Wisen Tanasa commented on JENKINS-58276 Re: Jira Cloud - Jenkins connectivity | Security measures Thanks for filing this ticket sanoop raj p s. Can you kindly share your learning, either here as comments or contribute to the project's documentation? Other people might have the same question and it'll be helpful for them to get what you have learnt from the source code. Thank you. 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.200340.1561969181000.455.1562133780290%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58276) Jira Cloud - Jenkins connectivity | Security measures
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58276 Jira Cloud - Jenkins connectivity | Security measures Change By: Wisen Tanasa Issue Type: Bug Improvement 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.200340.1561969181000.13296.1561999560917%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58276) Jira Cloud - Jenkins connectivity | Security measures
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58276 Jira Cloud - Jenkins connectivity | Security measures Change By: Wisen Tanasa Priority: Blocker Minor I am planning to connect to Jenkins from Jira Cloud using Webhooks.The purpose of the ticket is to get clarity on security measures in this solution.Can someone please elaborate on how security is taken care when triggering the build in Jenkins using Jira cloud webhook or vice versa.If we have any documents talking about the security of this scenario also will do! Expecting a fast reply as we are stuck on this. 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.200340.1561969181000.13293.1561999500322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin I normally use job-dsl-plugin to manage all my jobs i.e. I won't have the pain of managing multiple jobs. Do check it out. Alternatively, jira-trigger-plugin could support triggers DSL, but unfortunately I don't think I have the capacity to implement that at the moment. Feel free to contribute, the repository is community driven. 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.200156.1561013839000.7572.1561397460127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58112 Re: Triggering multibranch pipeline from jira-trigger-plugin Thanks for the detailed use case. A pattern matching won't suffice as you might want to trigger different workflow to different branches i.e. "Deploy in SIT" for "release branch", "Deploy in UAT" for "uat branch" (example), etc. Perhaps your best bet here is to get your branch triggered by an upstream project: deploy in uat job: configured with jira-trigger-plugin multibranch pipeline job: configured with upstream trigger to "deploy in uat job" (see: https://stackoverflow.com/questions/36825103/jenkins-trigger-multi-branch-pipeline-on-upstream-change) To be honest I'm not really sure if Multibranch job is really appropriate in your use case either, what I'm hearing is: release branch: sit deployment, uat deployment, prod deployment other branches: scm checkout, build, unit testing, packaging It sounds like they are an entirely different jobs that sharing one Jenkinsfile might not be appopriate? 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.200156.1561013839000.6936.1561354620097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering mulibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58112 Triggering mulibranch pipeline from jira-trigger-plugin Change By: Wisen Tanasa Issue Type: Bug New Feature 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.200156.1561013839000.6679.1561230360310%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering multibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58112 Triggering multibranch pipeline from jira-trigger-plugin Change By: Wisen Tanasa Summary: Triggering mulibranch multibranch pipeline from jira-trigger-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.200156.1561013839000.6681.1561230360335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering mulibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58112 Re: Triggering mulibranch pipeline from jira-trigger-plugin Thanks. I understand your problem that this is not supported at the moment. What I'm trying to understand better is the behaviour of jira-trigger-plugin that you're expecting if this plugin is supporting multibranch pipeline. So if you have development and release branch in your multibranch pipeline job, which branch would the plugin trigger? For example in git trigger, if there is a change in development branch, only development job is triggered. I'm not sure what are you expecting when multibranch pipeline job is configured with jira-trigger-plugin, trigger all branches build? Probably you can try given when then format. 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.200156.1561013839000.6677.1561230360271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58112) Triggering mulibranch pipeline from jira-trigger-plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58112 Re: Triggering mulibranch pipeline from jira-trigger-plugin Thanks for filing this issue. This is not a tested feature. Can you help me understand what are you trying to achieve: When a there is change in JIRA, which branch are you expecting to build? What are you expecting to be there but not there to make this functionality to work? When I read the documentation for multi branch pipeline, it seems like the only trigger that makes sense is a source control system like Git, that has branches. 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.200156.1561013839000.6645.1561187460115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect
Title: Message Title Wisen Tanasa commented on JENKINS-57814 Re: The unicode of Jira changelog maybe incorrect Thanks for getting back to this issue. I'm a little tight on my capacity at the moment and it's going to take sometime (few weeks) before I can have start looking into this issue. Feel free to contribute to the project though! 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.199766.1559546507000.1918.1560799200081%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect
Title: Message Title Wisen Tanasa closed an issue as Not A Defect Jenkins / JENKINS-57814 The unicode of Jira changelog maybe incorrect Change By: Wisen Tanasa 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.199766.1559546507000.20424.1559626440660%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect
Title: Message Title Wisen Tanasa commented on JENKINS-57814 Re: The unicode of Jira changelog maybe incorrect I believe I can't help you further on this one, feel free to re-open if the issue is moved to this 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.199766.1559546507000.20422.1559626440211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect
Title: Message Title Wisen Tanasa commented on JENKINS-57814 Re: The unicode of Jira changelog maybe incorrect I'm afraid this plugin has no control over the WebHook message generated from JIRA. I would suggest you to contact the JIRA support or community and see if you can fix the WebHook message. I think there is a bug in JIRA when the string is stored. There are "\ufffd" in both of the strings too. 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.199766.1559546507000.20420.1559626380164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect
Title: Message Title Wisen Tanasa commented on JENKINS-57814 Re: The unicode of Jira changelog maybe incorrect Have you tried entering the Chinese characters to the "JIRA field Matcher" directly? I'm guessing that the problem with entering "\u6dc7\ue1bd\u657c\u6d93\ufffd" in the field is, the backslash will be treated as just another String, hence the characters will not be treated as a unicode. 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.199766.1559546507000.20167.1559595180107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57818) When the JIRA Webhook only select the "Approved" status, there is Socket Timeout
Title: Message Title Wisen Tanasa commented on JENKINS-57818 Re: When the JIRA Webhook only select the "Approved" status, there is Socket Timeout We can't solve SocketTimeout issue for you unfortunately, seems like server configuration issue? Or is this happening to all configuration? In your use case however, JQL usage if optional. You can use the "JIRA Field Matcher" and match the status new value. 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.199772.1559564179000.20158.155959582%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping for email address
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-57630 Support Multi User Picker custom field parameter mapping for email address Change By: Wisen Tanasa Summary: Support Multi User Picker custom field parameter mapping for email address 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.199560.1558603816000.16869.1559250901169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Thanks for sharing them here 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.199560.1558603816000.16867.1559250841206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Deakey Tan Can you help share the solution / script that you're using here? It'll be very helpful for the community if they come across a similar requirement. 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.199560.1558603816000.16081.1559163000161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57701) Plugin not triggering jobs based on selected jql
Title: Message Title Wisen Tanasa commented on JENKINS-57701 Re: Plugin not triggering jobs based on selected jql Have you tried the Changelog Matcher? You can match the status there, instead of using JQL to avoid hitting JIRA. It sounds like a support or common question, I highly encourage you to ask the question in StackOverflow to get more help from the community, as per outlined here. 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.199640.1558969319000.12721.1558989480120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: Support Multi User Picker custom field parameter mapping Thanks for the confirmation. I've converted this issue as a new feature. Feel free to contribute! For a workaround, you can always use the injected JIRA_ISSUE_KEY environment variable, then hit JIRA and get the information by yourself. 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.199560.1558603816000.12104.1558879260111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Wisen Tanasa closed an issue as Won't Fix Jenkins / JENKINS-57620 JIRA Trigger not triggering on status change Change By: Wisen Tanasa Status: Open Closed Resolution: Won't Fix 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.199548.1558551175000.11998.1558815600197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) How to mapping Custom Field key in JIRA trigger plugin
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: How to mapping Custom Field key in JIRA trigger plugin Can you confirm if this is "Multi User Picker" field? It looks like an array to me. If it is, this is currently not supported yet. The currently supported fields can be seen at CustomFieldParameterResolverTest file. We welcome contribution, feel free to submit a pull request to support this feature. 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.199560.1558603816000.11992.1558815480229%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-57630 Support Multi User Picker custom field parameter mapping Change By: Wisen Tanasa Summary: How to Support Multi User Picker custom field parameter mapping Custom Field key in JIRA trigger 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.199560.1558603816000.11994.1558815480248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) Support Multi User Picker custom field parameter mapping
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-57630 Support Multi User Picker custom field parameter mapping Change By: Wisen Tanasa Issue Type: Bug New Feature 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.199560.1558603816000.11996.1558815480276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Wisen Tanasa commented on JENKINS-57620 Re: JIRA Trigger not triggering on status change I'm not sure about this one actually, sorry. It seems like configuration issue. Probably best to ask in Jenkins core community? 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.199548.1558551175000.11906.1558774440108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57630) How to mapping Custom Field key in JIRA trigger plugin
Title: Message Title Wisen Tanasa commented on JENKINS-57630 Re: How to mapping Custom Field key in JIRA trigger plugin What's the field type for that custom field? 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.199560.1558603816000.11904.1558774320117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57620) JIRA Trigger not triggering on status change
Title: Message Title Wisen Tanasa commented on JENKINS-57620 Re: JIRA Trigger not triggering on status change That's weird. Can you help share the "Webhook event body" for both the one that is working, and the one that is not? Seeing the whole event body will be helpful for troubleshooting. 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.199548.1558551175000.9563.1558560900155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Wisen Tanasa commented on JENKINS-55859 Re: jira-trigger-plugin not triggering build after creating issue Sounds good. The last time I check, when an issue is created, issue_updated event will be fired from Jira as well 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-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Wisen Tanasa commented on JENKINS-55859 Re: jira-trigger-plugin not triggering build after creating issue Please do the following to allow me to help you: Follow the instruction here: https://github.com/jenkinsci/jira-trigger-plugin/#troubleshooting Is this JIRA cloud of JIRA Server, what version? What version of Jenkins are you using? What version of jira-trigger-plugin are you using? 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-55862) jira-trigger-plugin logs not created
Title: Message Title Wisen Tanasa commented on JENKINS-55862 Re: jira-trigger-plugin logs not created Would you be able to provide the following: Current behaviour Expected behaviour Steps to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55374) JIRA Attachment Handling
Title: Message Title Wisen Tanasa commented on JENKINS-55374 Re: JIRA Attachment Handling Can you follow the troubleshooting instruction here and copy the webhook payload that you get? 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-55374) JIRA Attachment Handling
Title: Message Title Wisen Tanasa commented on JENKINS-55374 Re: JIRA Attachment Handling You should be able to JIRA field id to "attachment" under JIRA Field Matcher, without comparing new value or old value. The job hence will always be triggered when there are attachment changes. 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-55374) JIRA Attachment Handling
Title: Message Title Wisen Tanasa commented on JENKINS-55374 Re: JIRA Attachment Handling Thank you for the ticket. The jira-trigger-plugin is heavily relying on JIRA webhook feature, if the value that you are interested in is not available, it will not be available. I understand that you have managed to get your job triggered with status = Patch Available. One way you can achieve what you need is by utilising the jira-trigger-plugin injected environment variable, JIRA_ISSUE_KEY. You can use the issue key to hit JIRA back to retrieve the attachment information you need. 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-54548) Assistance with JQL Format
Title: Message Title Wisen Tanasa closed an issue as Cannot Reproduce Jenkins / JENKINS-54548 Assistance with JQL Format Change By: Wisen Tanasa 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54548) Assistance with JQL Format
Title: Message Title Wisen Tanasa commented on JENKINS-54548 Re: Assistance with JQL Format Yes, that's what I meant. No worries! Do reopen the issue if more assistance is needed. 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-54548) Assistance with JQL Format
Title: Message Title Wisen Tanasa commented on JENKINS-54548 Re: Assistance with JQL Format What I meant to say is, all of the other features in the plugin doesn't need "https:///configure". If you use JQL filter, the "https:///configure" will need to be configured properly. I'd expect an error to be logged, but if it's not anywhere I'm afraid I can't really help any further. Do let me know if the alternative provided works for you. 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-54548) Assistance with JQL Format
Title: Message Title Wisen Tanasa commented on JENKINS-54548 Re: Assistance with JQL Format Thanks for the detailed answer. Follow up questions: Have you configured the JIRA credentials in Jenkins as per mentioned in my comment? What do you configure as the value of ISSUENAME? ISSUE in JQL accepts ISSUE_KEY. For example, the JQL for this current ticket is ISSUE=JENKINS-54548. I don't understand how would you use that field to filter your job trigger. Alternatively, if you are trying to differentiate by ISSUE, the plugin injects JIRA_ISSUE_KEY as an environment variable. Would it be possible to execute your build conditionally based on that environment variable? 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-54548) Assistance with JQL Format
Title: Message Title Wisen Tanasa commented on JENKINS-54548 Re: Assistance with JQL Format Can you share the JQL you use? JQL is a JIRA feature, so it's best for you consult their documentation Can you share your logs? When JQL is used, Jenkins will need to talk back to JIRA. There might be a firewall issue, or you might have not configured the JIRA credentials in Jenkins. See: https://github.com/jenkinsci/jira-trigger-plugin/#jenkins-global-configuration-one-time 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-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Wisen Tanasa commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error I'm not an expert in JIRA, but I would have thought that "description" field is always mandatory. Do you have any thoughts on how this should have been tackled by 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Wisen Tanasa commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Can you provide the logs in FINE level as per the instruction here please? It will log out the content of the event that has been fired to 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53656) JIRA_ISSUE_KEY is not set in Pipeline jobs
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-53656 JIRA_ISSUE_KEY is not set in Pipeline jobs Change By: Wisen Tanasa Priority: Blocker Major 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-53656) JIRA_ISSUE_KEY is not set in Pipeline jobs
Title: Message Title Wisen Tanasa commented on JENKINS-53656 Re: JIRA_ISSUE_KEY is not set in Pipeline jobs This issue is only happening for Pipeline jobs, hence you can workaround the problem by creating a non Pipeline job (e.g. FreeStyle) that will be triggered by JIRA, which would next trigger a downstream pipeline job. 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-53656) JIRA_ISSUE_KEY is not set in Pipeline jobs
Title: Message Title Wisen Tanasa commented on JENKINS-53656 Re: JIRA_ISSUE_KEY is not set in Pipeline jobs Seems to be caused by a similar issue that has been resolved here: JENKINS-46482. The issue is happening due to the usage of EnvironmentContributingAction. 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-53656) JIRA_ISSUE_KEY is not set in Pipeline jobs
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-53656 JIRA_ISSUE_KEY is not set in Pipeline jobs Change By: Wisen Tanasa Summary: JIRA_ISSUE_KEY is not set in Pipeline jobs 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-53656) JIRA_ISSUE_KEY not set in Pipeline
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-53656 JIRA_ISSUE_KEY not set in Pipeline Change By: Wisen Tanasa Summary: Jira trigger plugin is JIRA_ISSUE_KEY not assigning environment variables to system set in Pipeline 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-53656) Jira trigger plugin is not assigning environment variables to system
Title: Message Title
Wisen Tanasa updated an issue
Jenkins / JENKINS-53656
Jira trigger plugin is not assigning environment variables to system
Change By:
Wisen Tanasa
Tried to retrieve the Env variable Jira issue key while running job. getting all the details except Jira details.Groovy code:: {code:java} import java.lang.* import java.util.* import java.io.* import java.net.* import groovy.lang.* import groovy.util.* import java.math.BigInteger import java.math.BigDecimal @NonCPS def printParams() { env.getEnvironment().each { name, value -> println "Name: $name -> Value $value" }fields.find { it.id == "JIRA_ISSUE_KEY" }.value } printParams() def env = System.getenv() //Print all the environment variables.env.each { println it } // You can also access the specific variable, say 'username', as show below String user= env['$JIRA_ISSUE_KEY']println user //println ${environment::get-variable('bamboo_buildNumber')}println "The issue is: ${env.JIRA_ISSUE_KEY}" {code}o/p:: JIRA_ISSUE_KEY value is getting null console o/p:: {code} JIRA issue is updated Running in Durability level: MAX_SURVIVABILITY [Pipeline] echo Name: BUILD_DISPLAY_NAME -> Value #65 [Pipeline] echo Name: BUILD_ID -> Value 65 [Pipeline] echo Name: BUILD_NUMBER -> Value 65 [Pipeline] echo Name: BUILD_TAG -> Value jenkins-PipeLine Navigator-65 [Pipeline] echo Name: BUILD_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/65/ [Pipeline] echo Name: CLASSPATH -> Value [Pipeline] echo Name: HUDSON_HOME -> Value C:\Users\SDWA-190\.jenkins [Pipeline] echo Name: HUDSON_SERVER_COOKIE -> Value 272877dd9d388ea0 [Pipeline] echo Name: HUDSON_URL -> Value http://localhost:8080/ [Pipeline] echo Name: JENKINS_HOME -> Value C:\Users\SDWA-190\.jenkins [Pipeline] echo Name: JENKINS_SERVER_COOKIE -> Value 272877dd9d388ea0 [Pipeline] echo Name: JENKINS_URL -> Value http://localhost:8080/ [Pipeline] echo Name: JOB_BASE_NAME -> Value PipeLine Navigator [Pipeline] echo Name: JOB_DISPLAY_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/display/redirect [Pipeline] echo Name: JOB_NAME -> Value PipeLine Navigator [Pipeline] echo Name: JOB_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/ [Pipeline] echo Name: RUN_CHANGES_DISPLAY_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/65/display/redirect?page=changes [Pipeline] echo Name: RUN_DISPLAY_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/65/display/redirect [Pipeline] echo LOCALAPPDATA=C:\Users\SDWA-190\AppData\Local [Pipeline] echo PROCESSOR_LEVEL=6 [Pipeline] echo FP_NO_HOST_CHECK=NO [Pipeline] echo VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\ [Pipeline] echo USERDOMAIN=SDWA-190-PC [Pipeline] echo LOGONSERVER= SDWA-190-PC [Pipeline] echo JAVA_HOME=C:\Program Files\Java\jdk1.8.0_102 [Pipeline] echo PROMPT=$P$G [Pipeline] echo SESSIONNAME=Console [Pipeline] echo ALLUSERSPROFILE=C:\ProgramData [Pipeline] echo PROCESSOR_ARCHITECTURE=AMD64 [Pipeline] echo
[JIRA] (JENKINS-53656) Jira trigger plugin is not assigning environment variables to system
Title: Message Title
Wisen Tanasa updated an issue
Jenkins / JENKINS-53656
Jira trigger plugin is not assigning environment variables to system
Change By:
Wisen Tanasa
Tried to retrieve the Env variable Jira issue key while running job. getting all the details except Jira details.Groovy code:: {code:java} import java.lang.* import java.util.* import java.io.* import java.net.* import groovy.lang.* import groovy.util.* import java.math.BigInteger import java.math.BigDecimal @NonCPS def printParams(){ env.getEnvironment().each{ name, value -> println "Name: $name -> Value $value" }fields.find { it.id == "JIRA_ISSUE_KEY" }.value } printParams()def env = System.getenv() //Print all the environment variables.env.each{ println it }// You can also access the specific variable, say 'username', as show below String user= env['$JIRA_ISSUE_KEY']println user//println ${environment::get-variable('bamboo_buildNumber')}println "The issue is: ${env.JIRA_ISSUE_KEY}" {code} o/p:: JIRA_ISSUE_KEY value is getting null console o/p:: {code} JIRA issue is updated Running in Durability level: MAX_SURVIVABILITY [Pipeline] echo Name: BUILD_DISPLAY_NAME -> Value #65 [Pipeline] echo Name: BUILD_ID -> Value 65 [Pipeline] echo Name: BUILD_NUMBER -> Value 65 [Pipeline] echo Name: BUILD_TAG -> Value jenkins-PipeLine Navigator-65 [Pipeline] echo Name: BUILD_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/65/ [Pipeline] echo Name: CLASSPATH -> Value [Pipeline] echo Name: HUDSON_HOME -> Value C:\Users\SDWA-190\.jenkins [Pipeline] echo Name: HUDSON_SERVER_COOKIE -> Value 272877dd9d388ea0 [Pipeline] echo Name: HUDSON_URL -> Value http://localhost:8080/ [Pipeline] echo Name: JENKINS_HOME -> Value C:\Users\SDWA-190\.jenkins [Pipeline] echo Name: JENKINS_SERVER_COOKIE -> Value 272877dd9d388ea0 [Pipeline] echo Name: JENKINS_URL -> Value http://localhost:8080/ [Pipeline] echo Name: JOB_BASE_NAME -> Value PipeLine Navigator [Pipeline] echo Name: JOB_DISPLAY_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/display/redirect [Pipeline] echo Name: JOB_NAME -> Value PipeLine Navigator [Pipeline] echo Name: JOB_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/ [Pipeline] echo Name: RUN_CHANGES_DISPLAY_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/65/display/redirect?page=changes [Pipeline] echo Name: RUN_DISPLAY_URL -> Value http://localhost:8080/job/PipeLine%20Navigator/65/display/redirect [Pipeline] echo LOCALAPPDATA=C:\Users\SDWA-190\AppData\Local [Pipeline] echo PROCESSOR_LEVEL=6 [Pipeline] echo FP_NO_HOST_CHECK=NO [Pipeline] echo VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\ [Pipeline] echo USERDOMAIN=SDWA-190-PC [Pipeline] echo LOGONSERVER= SDWA-190-PC [Pipeline] echo JAVA_HOME=C:\Program Files\Java\jdk1.8.0_102 [Pipeline] echo PROMPT=$P$G [Pipeline] echo SESSIONNAME=Console [Pipeline] echo ALLUSERSPROFILE=C:\ProgramData [Pipeline] echo PROCESSOR_ARCHITECTURE=AMD64 [Pipeline] echo
[JIRA] (JENKINS-53656) Jira trigger plugin is not assigning environment variables to system
Title: Message Title
Wisen Tanasa updated an issue
Jenkins / JENKINS-53656
Jira trigger plugin is not assigning environment variables to system
Change By:
Wisen Tanasa
Tried to retrieve the Env variable Jira issue key while running job. getting all the details except Jira details.Groovy code:: {code:java} import java.lang.* import java.util.* import java.io.* import java.net.* import groovy.lang.* import groovy.util.* import java.math.BigInteger import java.math.BigDecimal @NonCPS def printParams() { env.getEnvironment().each \\ { name, value -> println "Name: $name -> Value $value" } fields.find \ { it.id == "JIRA_ISSUE_KEY" }.value } printParams() def env = System.getenv() //Print all the environment variables. env.each { println it } // You can also access the specific variable, say 'username', as show below String user= env['$JIRA_ISSUE_KEY'] println user //println ${environment::get-variable('bamboo_buildNumber')} println "The issue is: ${env.JIRA_ISSUE_KEY}" o/p:: JIRA_ISSUE_KEY value is getting null console o/p:: JIRA issue is updated Running in Durability level: MAX_SURVIVABILITY [Pipeline] echo Name: BUILD_DISPLAY_NAME -> Value #65 [Pipeline] echo Name: BUILD_ID -> Value 65 [Pipeline] echo Name: BUILD_NUMBER -> Value 65 [Pipeline] echo Name: BUILD_TAG -> Value jenkins-PipeLine Navigator-65 [Pipeline] echo Name: BUILD_URL -> Value [ http://localhost:8080/job/PipeLine%20Navigator/65/ ] [Pipeline] echo Name: CLASSPATH -> Value [Pipeline] echo Name: HUDSON_HOME -> Value C:\Users\SDWA-190\.jenkins [Pipeline] echo Name: HUDSON_SERVER_COOKIE -> Value 272877dd9d388ea0 [Pipeline] echo Name: HUDSON_URL -> Value [ http://localhost:8080/ ] [Pipeline] echo Name: JENKINS_HOME -> Value C:\Users\SDWA-190\.jenkins [Pipeline] echo Name: JENKINS_SERVER_COOKIE -> Value 272877dd9d388ea0 [Pipeline] echo Name: JENKINS_URL -> Value [ http://localhost:8080/ ] [Pipeline] echo Name: JOB_BASE_NAME -> Value PipeLine Navigator [Pipeline] echo Name: JOB_DISPLAY_URL -> Value [ http://localhost:8080/job/PipeLine%20Navigator/display/redirect ] [Pipeline] echo Name: JOB_NAME -> Value PipeLine Navigator [Pipeline] echo Name: JOB_URL -> Value [ http://localhost:8080/job/PipeLine%20Navigator/ ] [Pipeline] echo Name: RUN_CHANGES_DISPLAY_URL -> Value [ http://localhost:8080/job/PipeLine%20Navigator/65/display/redirect?page=changes ] [Pipeline] echo Name: RUN_DISPLAY_URL -> Value [ http://localhost:8080/job/PipeLine%20Navigator/65/display/redirect ] [Pipeline] echo LOCALAPPDATA=C:\Users\SDWA-190\AppData\Local [Pipeline] echo PROCESSOR_LEVEL=6 [Pipeline] echo FP_NO_HOST_CHECK=NO [Pipeline] echo VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\ [Pipeline] echo USERDOMAIN=SDWA-190-PC [Pipeline] echo LOGONSERVER=SDWA-190-PC [Pipeline] echo JAVA_HOME=C:\Program Files\Java\jdk1.8.0_102 [Pipeline] echo PROMPT=$P$G [Pipeline] echo SESSIONNAME=Console [Pipeline] echo ALLUSERSPROFILE=C:\ProgramData [Pipeline] echo PROCESSOR_ARCHITECTURE=AMD64
[JIRA] (JENKINS-52719) Post Function Transition Event support
Title: Message Title Wisen Tanasa commented on JENKINS-52719 Re: Post Function Transition Event support This feature is not supported yet. At the moment the plugin is listening only to "changelog" webhook event, and it should look similar to this structure. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52719) Post Function Transition Event support
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-52719 Post Function Transition Event support Change By: Wisen Tanasa Summary: Jira-trigger: events sents from Jira don't trigger the job in Jenkins Post Function Transition Event support Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52719) Jira-trigger: events sents from Jira don't trigger the job in Jenkins
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-52719 Jira-trigger: events sents from Jira don't trigger the job in Jenkins Change By: Wisen Tanasa Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-52719) Jira-trigger: events sents from Jira don't trigger the job in Jenkins
Title: Message Title
Wisen Tanasa updated an issue
Jenkins / JENKINS-52719
Jira-trigger: events sents from Jira don't trigger the job in Jenkins
Change By:
Wisen Tanasa
Hello,We've added a webhook in Jira triggered by Comment Created and Issue updated, with the following SWL query:{code:java} project in ("Integrated Interior Platform","OIP 2.0","SSW Core") and issuetype in (Story,Task){code} . As the transition we're interested to use, Working to Verifying, has a custom event, StorytoWorking, we added a post function on it, to send also the event to the Hook, so this appears now in the webhook:TransitionsVerifying of IIP Story Workflow W/o DeliveredIn Jenkins, once the transition is done, I can see the event in logs:{code:java}Jul 24, 2018 10:52:58 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookWebhook event body:Jul 24, 2018 10:52:58 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook{"transition": {"workflowId": 924280,"workflowName": "IIP Story Workflow W/o Delivered","transitionId": 31,"transitionName": "Verifying","from_status": "Working","to_status": "Verifying"*strong text*{code}but the job isn't triggered. If I repeat the transition, I see comment_created, the second time, instead of issue_updated:{code:java}Jul 24, 2018 10:55:52 AM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookReceived Webhook callback from comment. Event type: comment_createdJul 24, 2018 10:56:08 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookWebhook event body:Jul 24, 2018 10:56:08 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook{"transition": {"workflowId": 924280,"workflowName": "IIP Story Workflow W/o Delivered","transitionId": 31,"transitionName": "Verifying","from_status": "Working","to_status": "Verifying"},{code}I've added the setup from Jira and Jenkins. Can you help?PS: By comment the job can be triggered.Thank you.
Add Comment
[JIRA] (JENKINS-52719) Jira-trigger: events sents from Jira don't trigger the job in Jenkins
Title: Message Title
Wisen Tanasa updated an issue
Jenkins / JENKINS-52719
Jira-trigger: events sents from Jira don't trigger the job in Jenkins
Change By:
Wisen Tanasa
Hello,We've added a webhook in Jira triggered by Comment Created and Issue updated, with the following SWL query: {code:java} project in ("Integrated Interior Platform","OIP 2.0","SSW Core") and issuetype in (Story,Task) {code} . As the transition we're interested to use, Working to Verifying, has a custom event, StorytoWorking, we added a post function on it, to send also the event to the Hook, so this appears now in the webhook:TransitionsVerifying of IIP Story Workflow W/o Delivered In Jenkins, once the transition is done, I can see the event in logs: {code:java} Jul 24, 2018 10:52:58 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookWebhook event body:Jul 24, 2018 10:52:58 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook{"transition": {"workflowId": 924280,"workflowName": "IIP Story Workflow W/o Delivered","transitionId": 31,"transitionName": "Verifying","from_status": "Working","to_status": "Verifying"*strong text* {code} but the job isn't triggered. If I repeat the transition, I see comment_created, the second time, instead of issue_updated: {code:java} Jul 24, 2018 10:55:52 AM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookReceived Webhook callback from comment. Event type: comment_createdJul 24, 2018 10:56:08 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhookWebhook event body:Jul 24, 2018 10:56:08 AM FINEST com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook{"transition": {"workflowId": 924280,"workflowName": "IIP Story Workflow W/o Delivered","transitionId": 31,"transitionName": "Verifying","from_status": "Working","to_status": "Verifying"}, {code} I've added the setup from Jira and Jenkins. Can you help? PS: By comment the job can be triggered.Thank you.
Add Comment
[JIRA] (JENKINS-47255) unable to trigger build from JIRA
Title: Message Title Wisen Tanasa commented on JENKINS-47255 Re: unable to trigger build from JIRA High likely caused by JQL misconfiguration. Close due to inactivity, please reopen otherwise. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47255) unable to trigger build from JIRA
Title: Message Title Wisen Tanasa closed an issue as Won't Fix Jenkins / JENKINS-47255 unable to trigger build from JIRA Change By: Wisen Tanasa Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43964) Two Build URLs appearing in JIRA comment
Title: Message Title Wisen Tanasa closed an issue as Fixed Jenkins / JENKINS-43964 Two Build URLs appearing in JIRA comment Change By: Wisen Tanasa Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43964) Two Build URLs appearing in JIRA comment
Title: Message Title Wisen Tanasa commented on JENKINS-43964 Re: Two Build URLs appearing in JIRA comment The problem of "one link" is fixed in 0.6.3. The root cause of the issue is the square brackets generated by the plugin as it interferes with JIRA wiki syntax. Before: Build is scheduled for: [http://jenkins.url, http://jenkins.url] After: Build is scheduled for: http://jenkins.url, http://jenkins.url The "two build URLs" problem seems to be caused by Jenkins not notifying the plugin correctly. This issue can't be reproduced now but can still theoretically happen. The workaround is to restart Jenkins. Please reopen this ticket with all of your Jenkins details and logs if this is still happening. This problem has happened in the past for pipeline job as per seen in this commit. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-43964) Two Build URLs appearing in JIRA comment
Title: Message Title Wisen Tanasa started work on JENKINS-43964 Change By: Wisen Tanasa Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Wisen Tanasa resolved as Fixed Jenkins / JENKINS-50125 Jenkins parameters missing in build when using jira trigger Change By: Wisen Tanasa Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Wisen Tanasa commented on JENKINS-50125 Re: Jenkins parameters missing in build when using jira trigger Fixed in 0.6.2. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33990) Polling support
Title: Message Title Wisen Tanasa commented on JENKINS-33990 Re: Polling support Confirmed that JIRA Cloud webhook is working with JIRA Trigger Plugin. We no longer need the polling support. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-33990) Polling support
Title: Message Title Wisen Tanasa closed an issue as Won't Do Jenkins / JENKINS-33990 Polling support Change By: Wisen Tanasa Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50125) Jenkins parameters missing in build when using jira trigger
Title: Message Title Wisen Tanasa started work on JENKINS-50125 Change By: Wisen Tanasa Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46836) JIRA Trigger Plugin fails job on null value attributes
Title: Message Title Wisen Tanasa commented on JENKINS-46836 Re: JIRA Trigger Plugin fails job on null value attributes Fixed under 0.6.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-46836) JIRA Trigger Plugin fails job on null value attributes
Title: Message Title Wisen Tanasa resolved as Fixed Jenkins / JENKINS-46836 JIRA Trigger Plugin fails job on null value attributes Change By: Wisen Tanasa Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
