[JIRA] (JENKINS-49789) NPE when attempting to parse exception
Title: Message Title
Alon Chanukov edited a comment on JENKINS-49789
Re: NPE when attempting to parse exception
We have had this happen 3 times in a row today(we placed 3 retrys around the stage), once yesterday and once about a week ago, We are using [Google Play Android Publisher|https://plugins.jenkins.io/google-play-android-publisher] 2.0 and [Google OAuth Credentials|https://plugins.jenkins.io/google-oauth-plugin] 0.9 on [Jenkins ver. 2.176.4|https://jenkins.io/] {code:java}18:01:45 Uploading 2 APK(s) with application ID: com..internal 18:01:45 18:01:45 APK file: app-internal-arm64-v8a-release.apk 18:01:45 SHA-1 hash:* 18:01:45 versionCode: 30010232 18:01:45 minSdkVersion: 2118:02:07 [Pipeline] } 18:02:07 [Pipeline] // script 18:02:07 [Pipeline] }18:02:07 ERROR: Execution failed18:02:07 java.lang.NullPointerException 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:102) 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:379) 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:194) 18:02:07 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) 18:02:07 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 18:02:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) 18:02:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 18:02:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 18:02:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 18:02:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 18:02:07 at java.lang.Thread.run(Thread.java:748) 18:02:07 Retrying{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-49789) NPE when attempting to parse exception
Title: Message Title Alon Chanukov commented on JENKINS-49789 Re: NPE when attempting to parse exception We have had this happen 3 times in a row today(we placed 3 retrys around the stage), once yesterday and once about a week ago, 18:01:45 Uploading 2 APK(s) with application ID: com..internal 18:01:45 18:01:45 APK file: app-internal-arm64-v8a-release.apk 18:01:45 SHA-1 hash:* 18:01:45 versionCode: 30010232 18:01:45 minSdkVersion: 21 18:02:07 [Pipeline] } 18:02:07 [Pipeline] // script 18:02:07 [Pipeline] } 18:02:07 ERROR: Execution failed 18:02:07 java.lang.NullPointerException 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:102) 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:379) 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:194) 18:02:07 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) 18:02:07 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 18:02:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) 18:02:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 18:02:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 18:02:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 18:02:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 18:02:07 at java.lang.Thread.run(Thread.java:748) 18:02:07 Retrying Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-49789) NPE when attempting to parse exception
Title: Message Title
Alon Chanukov edited a comment on JENKINS-49789
Re: NPE when attempting to parse exception
We have had this happen 3 times in a row today(we placed 3 retrys around the stage), once yesterday and once about a week ago,{code:java}18:01:45 Uploading 2 APK(s) with application ID: com..internal 18:01:45 18:01:45 APK file: app-internal-arm64-v8a-release.apk 18:01:45 SHA-1 hash:* 18:01:45 versionCode: 30010232 18:01:45 minSdkVersion: 2118:02:07 [Pipeline] } 18:02:07 [Pipeline] // script 18:02:07 [Pipeline] }18:02:07 ERROR: Execution failed 18:02:07 java.lang.NullPointerException 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:102) 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:379) 18:02:07 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:194) 18:02:07 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) 18:02:07 at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 18:02:07 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) 18:02:07 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 18:02:07 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 18:02:07 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 18:02:07 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 18:02:07 at java.lang.Thread.run(Thread.java:748) 18:02:07 Retrying {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-43400) Autofavorite broken on remote agents
Title: Message Title Alon Chanukov commented on JENKINS-43400 Re: Autofavorite broken on remote agents I am seeing this in logs often also. on BlueOcean 1.16.0 autofavorite plugin 1.2.4 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.180643.1491509101000.6526.1566340080367%40Atlassian.JIRA.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Alon Chanukov edited a comment on JENKINS-57158 Re: Pipeline is green but shows red in stage view I also had this happen reported to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS.This has happened with both regular pipeline and multi branch we upgraded pipeline-stage-tags-metadata 1.3.2 pipeline-stage-view 2.10 On Smithers Staging pipeline-stage-tags-metadata 1.3.8 On Smithers Staging pipeline-stage-view 2.11 among many other plugins, though those seem most applicable We also moved from 2.89.3 LTS to 2.164.3LTS 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.198908.1556031734000.20165.1559595120028%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Alon Chanukov edited a comment on JENKINS-57158 Re: Pipeline is green but shows red in stage view I also had this happen reported to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS.This has happened with both regular pipeline and multi branch we upgraded pipeline-stage-tags-metadata 1.3.2 pipeline-stage-view 2.10 On Smithers Staging pipeline-stage-tags-metadata 1.3.8 On Smithers Staging pipeline-stage-view 2.11 among many other plugins, though those seem most applicable We also moved from 2.89.3 LTS to 2.164.3LTS 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.198908.1556031734000.20161.1559595080213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Alon Chanukov edited a comment on JENKINS-57158 Re: Pipeline is green but shows red in stage view I also had this happen to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS.This has happened with both regular pipeline and multi branch we upgraded pipeline-stage-tags-metadata 1.3.2pipeline-stage-view 2.10On Smithers Staging pipeline-stage-tags-metadata 1.3.8On Smithers Staging pipeline-stage-view 2.11among many other plugins, though those seem most applicableWe also moved from 2.89.3 LTS to 2.164.3LTS !Screen Shot 2019-06-03 at 1.27.23 PM.png! PR pipelines 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.198908.1556031734000.20148.1559594160159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Alon Chanukov commented on JENKINS-57158 Re: Pipeline is green but shows red in stage view I also had this happen to me in prod twice in the 24 hours since I upgraded to latest started happening after we took in the Jenkins LTS. This has happened with both regular pipeline and multi branch we upgraded pipeline-stage-tags-metadata 1.3.2 pipeline-stage-view 2.10 On Smithers Staging pipeline-stage-tags-metadata 1.3.8 On Smithers Staging pipeline-stage-view 2.11 among many other plugins, though those seem most applicable We also moved from 2.89.3 LTS to 2.164.3LTS PR pipelines 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.198908.1556031734000.20144.1559594100743%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Alon Chanukov updated an issue Jenkins / JENKINS-57158 Pipeline is green but shows red in stage view Change By: Alon Chanukov Attachment: Screen Shot 2019-06-03 at 1.27.23 PM.png Attachment: Screen Shot 2019-06-03 at 1.26.54 PM.png 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.198908.1556031734000.20071.1559593740226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34818) Active Choice reactive parameter cannot access global parameters
Title: Message Title Alon Chanukov commented on JENKINS-34818 Re: Active Choice reactive parameter cannot access global parameters thanks for the work around but, is it impossible to have the plugin automatically do this code? it is very annoying to add this code every time i want to get a variable... I would imagine every user would like access to all global variables always. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [active-choices-plugin] (JENKINS-34818) Active Choice reactive parameter cannot access global parameters
Title: Message Title Alon Chanukov created an issue Jenkins / JENKINS-34818 Active Choice reactive parameter cannot access global parameters Issue Type: Bug Assignee: Bruno P. Kinoshita Attachments: Screen Shot 2016-05-13 at 10.23.27 AM.png, Screen Shot 2016-05-13 at 10.25.07 AM.png Components: active-choices-plugin Created: 2016/May/13 5:51 PM Environment: Jenkins 2.2 on a windows machine. Active Choices Plug-in 1.4 Priority: Major Reporter: Alon Chanukov In manage_jenkins System i under Global properties-->Environment variables I set a list of variables. I am unable to access any of them in my active choice parameter. see example of my usage below in images. If i simply switch the $DEVICES_MAP_DIR with the path that is shown in the global environment variable it works as expected using the global environment variable it fails. logs
[JIRA] [git-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
Alon Chanukov commented on JENKINS-23577 Add support for using branches in Git Parameter plugin Any update on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
Alon Chanukov commented on JENKINS-23577 Add support for using branches in Git Parameter plugin This is now mostly supported in the new version, but it does not sort the branches at all no mater the sorting options This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-parameter-plugin] (JENKINS-23577) Add support for using branches in Git Parameter plugin
Alon Chanukov edited a comment on JENKINS-23577 Add support for using branches in Git Parameter plugin This is now mostly supported in the new version, but it does not sort the branches at all no mater the sorting options, this makes the feature unusable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
