[JIRA] (JENKINS-59912) Im unable install any plugin im getting some timeout issues,
Title: Message Title Tobias Gruetzmacher assigned an issue to Unassigned Jenkins / JENKINS-59912 Im unable install any plugin im getting some timeout issues, Change By: Tobias Gruetzmacher Assignee: Tobias Gruetzmacher 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.202711.1571891293000.123.1571900340295%40Atlassian.JIRA.
[JIRA] (JENKINS-59912) Im unable install any plugin im getting some timeout issues,
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-59912 Im unable install any plugin im getting some timeout issues, Change By: Tobias Gruetzmacher Component/s: core Component/s: simple-theme-plugin Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202711.1571891293000.121.1571900340254%40Atlassian.JIRA.
[JIRA] (JENKINS-56574) Not able to install any pluggins
Title: Message Title Tobias Gruetzmacher updated an issue Jenkins / JENKINS-56574 Not able to install any pluggins Change By: Tobias Gruetzmacher Component/s: core Component/s: plugin-usage-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198189.1552628918000.125.1571900760180%40Atlassian.JIRA.
[JIRA] (JENKINS-56574) Not able to install any pluggins
Title: Message Title Tobias Gruetzmacher closed an issue as Not A Defect Looks like a network problem to me, not a Jenkins bug Jenkins / JENKINS-56574 Not able to install any pluggins Change By: Tobias Gruetzmacher Status: Open Closed Resolution: Not A Defect 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 vis
[JIRA] (JENKINS-59912) Im unable install any plugin im getting some timeout issues,
Title: Message Title Tobias Gruetzmacher commented on JENKINS-59912 Re: Im unable install any plugin im getting some timeout issues, I reassigned to core, since I don't see how this relates to any specific plugin. I suspect this is not even a bug, but a network problem, but haven't dug deeper how this error message might happen... Anyways, the issue tracker is not a support site - If you need quick answers, try the chat or mailing lists... 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.202711.1571891293000.129.1571901240247%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža commented on JENKINS-59840 Re: NullPointerException when activating the plugin Stefan, I have failed to reproduce this using same Jenkins version and your `.conf` and `.xml`. I am not aware of any recent changes around the actual spnego configuration and library version have not changed for sure. Can you retry with assertions enabled (-ea added as JVM argument)? The spnego library is relying on assertions to check the config sanity apparently, so we can get some actual diagnostics (which are otherwise hidden in production) this way. https://github.com/codelibs/spnego/blob/spnego-1.0.1/src/main/java/org/codelibs/spnego/SpnegoFilterConfig.java#L117 https://github.com/codelibs/spnego/blob/spnego-1.0.1/src/main/java/org/codelibs/spnego/SpnegoFilterConfig.java#L169 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.202575.157138872.131.1571902080128%40Atlassian.JIRA.
[JIRA] (JENKINS-59558) Add validation of id so that hyperlinks are generated correctly
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-59558 Add validation of id so that hyperlinks are generated correctly Change By: Ulli Hafner Summary: Hyperlink to result in project view not working Add validation of id so that hyperlinks are generated correctly 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.202191.1569578601000.133.1571902800150%40Atlassian.JIRA.
[JIRA] (JENKINS-59558) Add validation of id so that hyperlinks are generated correctly
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-59558 Add validation of id so that hyperlinks are generated correctly Change By: Ulli Hafner The step and freestyle configuration allows to provide a custom ID. This ID must be a valid URL, otherwise the plugin can't create valid hyperlinks . There should be some validation for this field. The hyperlinks to the warning results are not working -> see Screenshot ( left side gcc STM32F** Warnings )!image-2019-09-27-12-02-31-940.png! 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.202191.1569578601000.135.1571902920175%40Atlassian.JIRA.
[JIRA] (JENKINS-44450) Block scoped usage
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-44450 Block scoped usage Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/235 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.182278.1495543785000.144.1571904000844%40Atlassian.JIRA.
[JIRA] (JENKINS-44450) Block scoped usage
Title: Message Title Ulli Hafner commented on JENKINS-44450 Re: Block scoped usage I created a proof of concept: https://github.com/jenkinsci/warnings-ng-plugin/pull/235 Seems to need some additional work https://groups.google.com/d/msg/jenkinsci-dev/C3cQQSRWpqI/NJcSDsH9BwAJ. 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.182278.1495543785000.146.1571904120821%40Atlassian.JIRA.
[JIRA] (JENKINS-44450) Block scoped usage
Title: Message Title Ulli Hafner stopped work on JENKINS-44450 Change By: Ulli Hafner Status: In Progress Open 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.182278.1495543785000.157.1571905081350%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-59696
Re: support-core and thus advisor require to restart the instance to be activated
Maybe we should add a condition on Adding fine logging in ExtensionList, I found out that the extensions may be added twice when loading the { {DeadlockTrackChecker}} because of the call from [DeadlockTrackChecker|https://github.com/jenkinsci/support-core-plugin/blob/support-core-2.62/src/main/java/com/cloudbees/jenkins/support/timer/DeadlockTrackChecker.java#L30]. Which could be avoid there. But another call that could be causing this is the call to [ExtensionList.lookupSingleton|https://github.com/jenkinsci/support-core-plugin/blob/support-core-2.62/src/main/java/com/cloudbees/jenkins/support/filter/ ContentFilters .java # get L47] that can cause the {{ExtensionList } } to check be created is it does not exist yet: { code}return ExtensionList.lookupSingleton(ContentFilters.class); { instance code}A fix I have been testing is to do this instead:{code}return GlobalConfiguration . getInitLevel all (). compareTo get ( InitMilestone ContentFilters . EXTENSIONS_AUGMENTED class ) >= 0) ;{code } I have not been able to reproduce the issue using this method. This method goes through a different code path to get the component.I have added logging to the ExtensionsList class in this branch: https://github.com/Dohbedoh/jenkins/commit/0bf0178e43b8b8b42c82ba0938b4c53c2ead0c6dI noticed that when the issue happens:* the extension gets created when loading the {{DeadlockTrackChecker } } going through: https://github.com/Dohbedoh/jenkins/blob/JENKINS-59696/core/src/main/java/jenkins/model/Jenkins.java#L2641.* then the {{CompleteBatchJob}} refreshes the extensions and add it again [through the ExtensionList#refresh|https://github.com/Dohbedoh/jenkins/blob/JENKINS-59696/core/src/main/java/hudson/ExtensionList.java#L359-L360]I have attached logs in [^extension-loading-with-issue.log]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59914) When build step 'Upload app to AppCenter' changed build result to FAILURE in Jenkins
Title: Message Title Cristiana Tolea created an issue Jenkins / JENKINS-59914 When build step 'Upload app to AppCenter' changed build result to FAILURE in Jenkins Issue Type: Bug Assignee: Unassigned Components: appcenter-plugin Created: 2019-10-24 08:20 Environment: Jenkins ver. 2.176.1 AppCenter plugin ver. 07.0 Priority: Major Reporter: Cristiana Tolea I have just configured a Post-build action in Jenkins in order to upload the builds to AppCenter. After the new build is created successfully by gradle, the Upload to AppCenter task starts and returns the following exceptions, causing the build to fail: Creating an upload resource. io.jenkins.plugins.appcenter.AppCenterException: Create upload resource unsuccessful: at io.jenkins.plugins.appcenter.task.internal.CreateUploadResourceTask.lambda$execute$0(CreateUploadResourceTask.java:48) at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760) at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736) at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977) at retrofit2.CompletableFutureCallAdapterFactory$BodyCallAdapter$2.onResponse(CompletableFutureCallAdapterFactory.java:81) at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:129) at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174) at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thr
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Allan BURDAJEWICZ updated JENKINS-59696 Jenkins / JENKINS-59696 support-core and thus advisor require to restart the instance to be activated Change By: Allan BURDAJEWICZ Status: In Progress Review 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.202395.1570521598000.169.1571905740609%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-59696 Change By: Allan BURDAJEWICZ Status: Open In Progress 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.202395.1570521598000.167.1571905740580%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title Jakub L commented on JENKINS-59907 Re: sh steps stuck indefinitely after upgrading durable-task to v1.31 This is NOT related to the other two opened issues with v1.31. Those two are likely caused by the new binary durable_task_monitor not being available from within Docker containers. But this issue is caused by the binary not being executable on my HW architecture. I'll clarify the title. 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.202658.1571858325000.174.1571907660256%40Atlassian.JIRA.
[JIRA] (JENKINS-59915) SVN_REVISION, SVN_URL missing in subversion plugin 2.12.1
Title: Message Title shravan Bommu created an issue Jenkins / JENKINS-59915 SVN_REVISION, SVN_URL missing in subversion plugin 2.12.1 Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2019-10-24 09:02 Environment: Jenkins 2.176.1, svn version 2.12.1 Priority: Critical Reporter: shravan Bommu Am using Pipeline script from SCM I want to give SVN_URL as build parameter to build job. Am trying to print SVN_URL print the SVN_URL_1 in pipeline line script of build job. Error is: groovy.lang.MissingPropertyException: No such property: $SVN_URL_1 for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) When I use env.SVN_URL_1, it is printing NULL. Add Comme
[JIRA] (JENKINS-59907) sh steps stuck indefinitely on uncommon architectures (e.g. s390x)
Title: Message Title Jakub L updated an issue Jenkins / JENKINS-59907 sh steps stuck indefinitely on uncommon architectures (e.g. s390x) Change By: Jakub L Summary: sh steps stuck indefinitely after upgrading durable-task to v1 on uncommon architectures (e . 31 g. s390x) 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.202658.1571858325000.177.1571907780515%40Atlassian.JIRA.
[JIRA] (JENKINS-59864) Job can stuck forever after message wlrun killed
Title: Message Title Aliaksandr Kavaliou commented on JENKINS-59864 Re: Job can stuck forever after message wlrun killed Hi Maria. Will try and get back. 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.202602.1571646097000.183.1571908980220%40Atlassian.JIRA.
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title lucamilanesio updated JENKINS-59745 Jenkins / JENKINS-59745 Error when trying to vote on label in multibranch pipeline (0.3.4) Change By: lucamilanesio Status: In Progress Review 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.202464.1570786202000.187.1571909940930%40Atlassian.JIRA.
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title lucamilanesio started work on JENKINS-59745 Change By: lucamilanesio Status: Open In Progress 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.202464.1570786202000.185.1571909940698%40Atlassian.JIRA.
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title lucamilanesio updated JENKINS-59745 Thanks, Thomas Draebing for reporting and also fixing this. Jenkins / JENKINS-59745 Error when trying to vote on label in multibranch pipeline (0.3.4) Change By: lucamilanesio Status: In Review Resolved Resolution: Fixed Released As: gerrit-code-review-0.3.5 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- Y
[JIRA] (JENKINS-59915) SVN_REVISION, SVN_URL missing in subversion plugin 2.12.1
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect please use the google groups to ask questions https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Jenkins / JENKINS-59915 SVN_REVISION, SVN_URL missing in subversion plugin 2.12.1 Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect 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 jen
[JIRA] (JENKINS-52264) Error while running pipeline job in docker
Title: Message Title Giorgio Desideri commented on JENKINS-52264 Re: Error while running pipeline job in docker In my scripted pipeline `-v /var/jenkins/caches:/var/jenkins/caches` it works as work-around. 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.192029.153025197.193.1571912340238%40Atlassian.JIRA.
[JIRA] (JENKINS-52264) Error while running pipeline job in docker
Title: Message Title
Giorgio Desideri edited a comment on JENKINS-52264
Re: Error while running pipeline job in docker
In my scripted pipeline ` {{-v /var/jenkins/caches:/var/jenkins/caches}} ` it works as work-around. {{}}{{docker.image("").inside("{{-v /var/jenkins/caches:/var/jenkins/caches}}") }}{{{}}{{...}}{{}}}
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.192029.153025197.200.1571912400257%40Atlassian.JIRA.
[JIRA] (JENKINS-52264) Error while running pipeline job in docker
Title: Message Title
Giorgio Desideri edited a comment on JENKINS-52264
Re: Error while running pipeline job in docker
In my scripted pipeline {{-v /var/jenkins/caches:/var/jenkins/caches}} it works as work-around.{{ }}{{ docker.image("").inside("{{-v /var/jenkins/caches:/var/jenkins/caches}}") }} { {{}} {{...}} {{}}}
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.192029.153025197.207.1571912520260%40Atlassian.JIRA.
[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows
Title: Message Title James Howe commented on JENKINS-59867 Re: NodeJS tool installation fails on Windows My guess was something to do with the old MAX_PATH limit, but if it's only Windows 2019 that's more odd. 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.202606.1571659896000.214.1571913780244%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) support-core and thus advisor require to restart the instance to be activated
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-59696
Re: support-core and thus advisor require to restart the instance to be activated
Can reproduce in core 2.201 but not consistently. Sometimes it happens, sometimes no. To reproduce it consistently, I launch the plugin install and refresh the main page or the {{$JENKINS_URL/support}} aggressively (but manually :) ).I wonder if there is a race condition somewhere. Maybe one of the Support Core component (like the [SlowRequestChecker|https://github.com/jenkinsci/support-core-plugin/blob/support-core-2.62/src/main/java/com/cloudbees/jenkins/support/slowrequest/SlowRequestChecker.java]) starts before the PluginManager has finished to load the plugin dynamically, which causes the same extension of {{ContentFilters}} to be loaded twice (In the ExtensionList, the 2 instances of {{ContentFilters}} are the same object). Maybe _SlowRequestChecker_ starts too soon.
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.202395.1570521598000.217.1571914980288%40Atlassian.JIRA.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Brian J Murrell updated an issue Jenkins / JENKINS-53649 Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable Change By: Brian J Murrell Attachment: image-2019-10-24-07-05-23-113.png 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.194144.1537309242000.235.1571915161118%40Atlassian.JIRA.
[JIRA] (JENKINS-59714) Remove the pinned status from the exported plugin lists
Title: Message Title Arnaud Héritier updated JENKINS-59714 Jenkins / JENKINS-59714 Remove the pinned status from the exported plugin lists Change By: Arnaud Héritier Status: In Review Fixed but Unreleased Resolution: Fixed Released As: support-core-2.63 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.202423.1570628855000.237.1571915640844%40Atlassian.JIRA.
[JIRA] (JENKINS-59916) SSRF on https://issues.jenkins-ci.org/
Title: Message Title Wayc0de created an issue Jenkins / JENKINS-59916 SSRF on https://issues.jenkins-ci.org/ Issue Type: Bug Assignee: Unassigned Components: jira-issue-updater-plugin, jira-plugin Created: 2019-10-24 11:13 Environment: Jira v7.13.6 Labels: jira Priority: Major Reporter: Wayc0de Hi Security Team, Summary The /plugins/servlet/gadgets/makeRequest resource in Jira before version 8.4.0 allows remote attackers to access the content of internal network resources via a Server Side Request Forgery (SSRF) vulnerability due to a logic bug in the JiraWhitelist class. CVE-2019-8451 is a pre-authentication server side request forgery (SSRF) vulnerability found in the /plugins/servlet/gadgets/makeRequest resource. The vulnerability exists due to “a logic bug” in the JiraWhitelist class. An unauthenticated attacker could exploit this vulnerability by sending a specially crafted web request to a vulnerable Jira server. Successful exploitation would result in unauthorized access to view and potentially modify internal network resources. The vulnerability was first introduced in Jira Core and Jira Software versions 7.6.0, an enterprise release in November 2017, and affects Jira Core and Software versions from 7.6.0 through 8.3.4. Steps To Reproduce: 1. Target is https://issues.jenkins-ci.org/ use Atlassian Jira Project Management Software (v7.13.6) 2. Lets rock! wayc0de@DESKTOP-9C0TVKV:~/tools/CVE-2019-8451$ python CVE-2019-8451.py https://issues.jenkins-ci.org Result : SSRF URL: www.baidu.com Send poc Success! X-AUSERNAME= anonymous vuln_url= https://i
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
Brian J Murrell commented on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Matt C. Wilson Even using {{label:}}s produces inconsistent results: Those two steps in the red box are both of the form:
sh label: ,
script: '''...'''
The first one is in the steps portion of the stage and looks like:
sh label: env.STAGE_NAME,
script: '''...'''
and the second one is in the post->success portion of the stage and looks like:
sh label: "Collect artifacts",
script: '''...'''
But as you can see, they are displayed quite differently.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message b
[JIRA] (JENKINS-59917) Jenkins Health Advisor for offline instances
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59917 Jenkins Health Advisor for offline instances Issue Type: New Feature Assignee: Unassigned Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-24 11:19 Priority: Minor Reporter: Arnaud Héritier The current architecture of Jenkins Health Advisor by CloudBees is relying on a server maintained and regularly update by the CloudBees Support team. When an instance isn't connected to internet it cannot send a support bundle for being analysed automatically. A solution not too much expensive could be to provide a front-end with a form where we ask the email to use and the support bundle to analyse (to be generated manually on the offline infrastructure). Even if this is a server improvement, I am tracking it here on the plugin side to give the visibility to the community Add Comment
[JIRA] (JENKINS-59918) labels and step script content shown inconsistently in blue ocean steps
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-59918 labels and step script content shown inconsistently in blue ocean steps Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-10-24 11:20 Environment: Jenkins ver. 2.190.1 Blue Ocean - BlueOcean Aggregator - 1.19.0 Priority: Major Reporter: Brian J Murrell Somewhat related to JENKINS-53649 and as described there, but this feels like it deserves it's own ticket. The content of a step in the B/O step summary seems inconsistent: Those two steps in the red box are both of the form: sh label: , script: '''...''' The first one is in the steps portion of the stage and looks like: sh label: env.STAGE_NAME, script: '''...''' and the second one is in the post->success portion of the stage and looks like: sh label: "Collect artifacts", script: '''...''' But as you can
[JIRA] (JENKINS-59918) labels and step script content shown inconsistently in blue ocean steps
Title: Message Title
Brian J Murrell updated an issue
Jenkins / JENKINS-59918
labels and step script content shown inconsistently in blue ocean steps
Change By:
Brian J Murrell
Somewhat related to JENKINS-53649 and as described there, but this feels like it deserves it's own ticket.The content of a step in the B/O step summary seems inconsistent: ! image https://issues.jenkins - ci.org/secure/attachment/49301/49301_image- 2019-10-24-07-05-23-113.png!Those two steps in the red box are both of the form:{noformat}sh label: , script: '''...'''{noformat}The first one is in the {{steps}} portion of the stage and looks like:{noformat}sh label: env.STAGE_NAME, script: '''...'''{noformat}and the second one is in the {{post}}->{{success}} portion of the stage and looks like:{noformat} sh label: "Collect artifacts", script: '''...'''{noformat}But as you can see, they are displayed quite differently. But why?It doesn't seem like they should be. The second step shouldn't have the label prefixed with the script content of step.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
Brian J Murrell edited a comment on JENKINS-53649
Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
[~mcw] Even using \{{label:}}s produces inconsistent results:!image-2019-10-24-07-05-23-113.png!Those two steps in the red box are both of the form:{noformat}sh label: , script: '''...'''{noformat}The first one is in the {{steps}} portion of the stage and looks like:{noformat}sh label: env.STAGE_NAME, script: '''...'''{noformat}and the second one is in the {{post}}->{{success}} portion of the stage and looks like:{noformat} sh label: "Collect artifacts", script: '''...'''{noformat} But as you can see, they are displayed quite differently. I've opened JENKINS-59918 about this, FWIW.
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.194144.1537309242000.276.1571916120899%40Atlassian.JIRA.
[JIRA] (JENKINS-56768) Unable to switch to a sudo user using ssh pipeline
Title: Message Title Naresh Rayapati commented on JENKINS-56768 Re: Unable to switch to a sudo user using ssh pipeline Tharun Reddy I hope you are adding sudo: true option for those commands? passwordless sudo access doesn't require that option. 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.198411.1553644739000.280.1571916900334%40Atlassian.JIRA.
[JIRA] (JENKINS-59168) Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system"
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-59168 Re: Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system" Hello Aliaksandr Kavaliou, It is available since 5.9. Regards, Rolando 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.201605.1567267759000.285.1571917320408%40Atlassian.JIRA.
[JIRA] (JENKINS-59168) Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system"
Title: Message Title Rolando-Mihai Vlad updated an issue Jenkins / JENKINS-59168 Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system" Change By: Rolando-Mihai Vlad Attachment: image-2019-10-24-14-41-34-599.png 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.201605.1567267759000.283.1571917320327%40Atlassian.JIRA.
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Andrey Belyaevskiy created an issue Jenkins / JENKINS-59919 plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task Issue Type: Bug Assignee: Alex Earl Components: email-ext-plugin Created: 2019-10-24 12:13 Environment: jenkins 2.7.4, email ext plugin 2.58 Priority: Major Reporter: Andrey Belyaevskiy I have downstream job. When this job is triggered by more than one upstream builds it takes developers only from first build. My setup is jobA->jobB If jobB with some run number x is triggered by jobA with number y and number y+1, and jobB x fails ext email plugin takes developers from jobA x build for culprits list and developers from joB x+1 build do not receive email about failed downstream job. Add Comment
[JIRA] (JENKINS-42655) Active choices parameters not rendering after dsl generation
Title: Message Title Romain DEQUIDT commented on JENKINS-42655 Re: Active choices parameters not rendering after dsl generation Same issue here: Upload job via generated DSL job. Parameters aren't populated. Click Configure for job, and immediately save. Job notes that manual changes have been made. Parameters now are populated as expected by script. Versions: Script Security Plugin - 1.54 Active Choices Plug-in - 2.1 Jenkins Version - 2.176.1 Any update? 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.179605.1489140109000.290.1571919300296%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title
Stefan commented on JENKINS-59840
Re: NullPointerException when activating the plugin
With asserts on, I am seeing:
java.lang.IllegalArgumentException: The client module name was not found in the login file: spnego-client
at org.codelibs.spnego.SpnegoFilterConfig.moduleExists(SpnegoFilterConfig.java:383)
at org.codelibs.spnego.SpnegoFilterConfig.doClientModule(SpnegoFilterConfig.java:169)
...
I unpacked the *.jar files in our jre (java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64) and can see the configured class:
# find -name Krb5LoginModule.class
./com/sun/security/auth/module/Krb5LoginModule.class
Some other things I have noticed: With 1.6, the file where the plugin saves it's config has been renamed kerberos-sso.xml => com.sonymobile.jenkins.plugins.kerberossso.PluginImpl.xml. I tried any combination of names, both files present/absent but can still only enable the plugin via CasC. With no CasC, plugin installed but deactivated I can see this when strace'ing a freshly started java process:
29455 openat(AT_FDCWD, "/var/lib/jenkins/./kerberos.conf", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOTDIR (Not a directory)
29455 openat(AT_FDCWD, "/tmp/kerberos.conf", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOTDIR (Not a directory)
So something tries to open these paths as directory. When I then try to activate the plugin, I can see stats on the config file:
29439 stat("/var/lib/jenkins/kerberos.conf", {st_mode=S_IFREG|0644, st_size=1059, ...}) = 0
29439 stat("/var/lib/jenkins/kerberos.conf", {st_mode=S_IFREG|0644, st_size=1059, ...}) = 0
29439 stat("/var/lib/jenkins/kerberos.conf", {st_mode=S_IFREG|0644, st_size=1059, ...}) = 0
With CasC the order changes and the plugin is enabled:
30937 stat("/var/lib/jenkins/kerberos.conf",
30937 stat("/var/lib/jenkins/kerberos.conf", {st_mode=S_IFREG|0644, st_size=1059, ...}) = 0
30937 open("/var/lib/jenkins/kerberos.conf", O_RDONLY
30937 openat(AT_FDCWD, "/var/lib/jenkins/./kerberos.conf", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOTDIR (Not a directory)
30937 openat(AT_FDCWD, "/tmp/kerberos.conf", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOTDIR (Not a directory)
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Stefan updated an issue Jenkins / JENKINS-59840 NullPointerException when activating the plugin Change By: Stefan Attachment: assert.txt 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.202575.157138872.301.1571920620402%40Atlassian.JIRA.
[JIRA] (JENKINS-59168) Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system"
Title: Message Title Aliaksandr Kavaliou edited a comment on JENKINS-59168 Re: Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system" Great. Thank you Ronaldo Rolando 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.201605.1567267759000.305.1571921400358%40Atlassian.JIRA.
[JIRA] (JENKINS-59168) Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system"
Title: Message Title Aliaksandr Kavaliou commented on JENKINS-59168 Re: Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system" Great. Thank you Ronaldo 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.201605.1567267759000.303.1571921400268%40Atlassian.JIRA.
[JIRA] (JENKINS-59920) JsonSlurper errors within Jenkins Pipeline
Title: Message Title
Vinod Radhakrishnan created an issue
Jenkins / JENKINS-59920
JsonSlurper errors within Jenkins Pipeline
Issue Type:
Bug
Assignee:
vjuranek
Attachments:
Pipeline-error.docx
Components:
groovy-plugin, pipeline
Created:
2019-10-24 13:29
Labels:
pipeline jenkins
Priority:
Blocker
Reporter:
Vinod Radhakrishnan
I am trying to use jsonslurper class within my Jenkinsfile and pipeline and it throws the below error. Caused: java.io.NotSerializableException: groovy.json.internal.LazyMap My jenkins file given below. #!groovy import groovy.json.JsonSlurper def json_str = '''{ "name": "Foo Bar", "year": 2018, "timestamp": "2018-03-08T00:00:00", "tags": [ "person", "employee" ], "grade": 3.14 }''' def jsonSlurper = new JsonSlurper() cfg = jsonSlurper.parseText(json_str) println(cfg) pipeline { agent \{ label 'python' } options { timestamps() buildDiscarder(logRotator(numToKeepStr: '15', artifactNumToKeepStr: '15')) } environment { teamName = "devops" appName = "demo" packageName = 'demo' } stages { stage ('Deploy to dev') { steps { echo 'Deploying Testtt' } } } } The moment it enters the pipeline part, the job errors out. I have attached the detailed logs as an attachment. I went through many blogs and people recommend to use jsonslurperclassic as a workaround and I get that. The same code works fine through our prodcution Jenkins Ecosystem. Is this something related to any plugin version. Why does the job fail even though the am not using the method inside the pipeline. I read an interesting blog post where it mentions Jenkins job tries to sa
[JIRA] (JENKINS-59921) How to update the status of an Jira issue from Jenkins piepline
Title: Message Title Pavan Yadala created an issue Jenkins / JENKINS-59921 How to update the status of an Jira issue from Jenkins piepline Issue Type: Task Assignee: Naresh Rayapati Components: jira-issue-updater-plugin, jira-plugin, jira-steps-plugin, jira-trigger-plugin Created: 2019-10-24 14:14 Labels: plugin jenkins jira-plugin-2.4 pipeline jira Priority: Minor Reporter: Pavan Yadala I want to update the status of an issue in Jira after my jenkins job build is successful. If i try to update the status, system throws unknown parameter. WARNING: Unknown parameter(s) found for class type 'org.thoughtslive.jenkins.plugins.jira.steps.EditIssueStep': status Is there a way to update the status of an Jira issue? Add Comment
[JIRA] (JENKINS-59921) How to update the status of an Jira issue from Jenkins piepline
Title: Message Title Pavan Yadala updated an issue Jenkins / JENKINS-59921 How to update the status of an Jira issue from Jenkins piepline Change By: Pavan Yadala Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202720.1571926465000.311.1571926980211%40Atlassian.JIRA.
[JIRA] (JENKINS-59922) Publish should use p4 reconcile -t to detect filetype changes
Title: Message Title Karl Wirth created an issue Jenkins / JENKINS-59922 Publish should use p4 reconcile -t to detect filetype changes Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2019-10-24 14:28 Environment: P4-Plugin 1.10.5 Priority: Major Reporter: Karl Wirth When a file changes from being a symlink to a text file (using the same name) P4jenkins wont detect it properly because 'p4 reconcile' is not using the '-t' flag. This causes problems later in the job: P4 Task: reconcile files to changelist. ... p4 revert -k //jenkins-Windows10-SymlinkEdgeCases_WindowsOnly-9/... +... p4 sync -k //jenkins-Windows10-SymlinkEdgeCases_WindowsOnly-9/... +... p4 reconcile -e -a -f //jenkins-Windows10-SymlinkEdgeCases_WindowsOnly-9/.___ +... p4 opened -Cjenkins-Windows10-SymlinkEdgeCases_WindowsOnly-9 //jenkins-Win___ +duration: (24ms) P4 Task: publish files to Perforce. ... p4 change -i +... p4 change -o 2047 +... pending change: 2047 ... p4 reopen -c2047 //jenkins-Windows10-SymlinkEdgeCases_WindowsOnly-9/... +... p4 change -o 2047 +... p4 opened -Cjenkins-Windows10-SymlinkEdgeCases_WindowsOnly-9 //jenkins-Win___ +... ... edit //depot/SymlinkEdgeCases/Windows/SymLinks/windows_file_symlink ... submitting files ... p4 describe -s 2047 +... p4 fixes -c2047 +... p4 submit -i + Unable to publish workspace: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s): Client side operation(s) failed. Command aborted. Build step 'Perforce: Publish assets' marked build as failure Finished:
[JIRA] (JENKINS-59923) Repo Manifest action clashes with the built in Tags action
Title: Message Title Simon Williams created an issue Jenkins / JENKINS-59923 Repo Manifest action clashes with the built in Tags action Issue Type: Bug Assignee: Simon Williams Components: repo-plugin Created: 2019-10-24 14:30 Environment: Jenkins: 2.190.1 REPO plugin: 1.10.7 Priority: Major Reporter: Simon Williams I have created a Pipeline job, which pulls the Jenkinsfile from Git. The Jenkinsfile then uses the repo-plugin to pull the code to build from Gerrit. Following a build, I am left with two action buttons: "No Tags" "Repo Manifest" The Repo Manifest usually loads a page that shows the manifest file used for the build, however because it has been implemented as an AbstractScmTagAction it results in generating the same URL (.../tagBuild/), and so the tag build action page is shown instead of the manifest page.
[JIRA] (JENKINS-59923) Repo Manifest action clashes with the built in Tags action
Title: Message Title Simon Williams started work on JENKINS-59923 Change By: Simon Williams Status: Open In Progress 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.202722.1571927424000.314.1571927460240%40Atlassian.JIRA.
[JIRA] (JENKINS-59924) Allow providing passphrase for RSA private key in ec2 plugin
Title: Message Title Abhinav Varshney created an issue Jenkins / JENKINS-59924 Allow providing passphrase for RSA private key in ec2 plugin Issue Type: Improvement Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-10-24 14:51 Labels: ec2-plugin Priority: Major Reporter: Abhinav Varshney Currently the plugin throws an exception when a RSA private key (with passphrase) is provided. there is no text box to provide the passphrase. This is preventing us from creating the EC2 instances. Since the Generate Key option throws a null pointer as highlighted in some other jiras, this is blocker for using the EC2 plugin. Exception when "Test connection" is clicked. Stack trace java.io.IOException: This private key is password protected, which isn't supported yet at hudson.plugins.ec2.EC2PrivateKey.getFingerprint(EC2PrivateKey.java:83) at hudson.plugins.ec2.EC2PrivateKey.find(EC2PrivateKey.java:112) at hudson.plugins.ec2.EC2Cloud$DescriptorImpl.doTestConnection(EC2Cloud.java:932) at hudson.plugins.ec2.AmazonEC2Cloud$DescriptorImpl.doTestConnection(AmazonEC2Cloud.java:214) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.k
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Alex Earl commented on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task I'm not sure I understand the issue here. jobA is run twice and it triggers TWO runs of jobB or just one? Which recipient provider are you using in your jobB? If I assume UpstreamCommitters, then the following code is used: https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java#L51 This uses the UpstreamCause to determine what triggered the build, this should resolve to the correct upstream instance of jobA if two jobB's are triggered (one for each trigger of jobA). If only one jobB is triggered, then only one jobA will be the upstream cause. 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.202718.1571919183000.318.1571929320242%40Atlassian.JIRA.
[JIRA] (JENKINS-59925) Parametrized pipelines do not get parameters for GIT URL
Title: Message Title
Luca Gioppo created an issue
Jenkins / JENKINS-59925
Parametrized pipelines do not get parameters for GIT URL
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-10-24 15:07
Environment:
Linux
Priority:
Minor
Reporter:
Luca Gioppo
We are trying to use a parametrized pipeline passing a string parameter called "REPONAME" and than choosing the "Pipeline script from SCM" and entering as "Repository URL" the following string: https://gitlab.csi.it/technical-components/tecnologie/container/${REPONAME}.git in GIT we use the webhook as this: http://tst-jenkins-master.ecosis.csi.it/project/TEST_DOCKER_PIPELINE/docker-pipeline-globaleaks/buildWithParameters?token=4e9b91e3a3124e8082b443b9d2873a8c&REPONAME=globaleaks The build console show us that the REPONAME variable is empty and does not get substituted in the process. We already set the "Lightweight checkout" unchecked (with the option checked on the error is even worse) The console output is: Checking out git https://gitlab.csi.it/technical-components/tecnologie/container/${REPONAME}.git into /var/lib/jenkins/workspace/TEST_DOCKER_PIPELINE/docker-pipeline-globaleaks@script to read Jenkinsfile using credential csi-gitlab > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://gitlab.csi.it/technical-components/tecnologie/container/.git # timeout=10 Fetching upstream changes from https://gitlab.csi.it/technical-components/tecnologie/container/.git > git --version # timeout=10 using GIT_ASKPASS to set credentials csi-gitlab Setting http proxy: proxy-srv.csi.it:3128 > git fetch --tags --progress https://gitlab.csi.it/technical-components/tecnologie/container/.git +refs/heads/:refs/remotes/or
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Jeremy Page edited a comment on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost - We have branches disappear when there is a PR pending for them using Github. -Sorry for the confusion, I did not know how to configure the job properly. Thank you [~morganr87] 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.196298.154504211.328.1571930402426%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Esther Álvarez Feijoo commented on JENKINS-59844 Re: Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command After talking with Ramon Leon, we agreed that: Given that the exception is documented in downstream jdk class (ProcessBuilder), it can have been handled already by some client, so changing this exception for another can have unexpected consequences in any plugin using hudson.Launcher ProcessBuilder is being used in several other classes in jenkins. To be consistent we should handle this exception equally, increasing the number of interface changes. The objective is to make clearer the cause of this exception, so the least risky solution is: Showing a log before invoking the Launcher, when the command is empty, informing the user that this can cause unexpected behaviour. This should help any user to track down the cause of this exception in the future. Complete Launcher's javadoc informing about that a RuntimeException can be thrown because of that reason. I'm creating a PR with these little changes Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are su
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Mikhail Ianchikov updated an issue Jenkins / JENKINS-59919 plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task Change By: Mikhail Ianchikov Attachment: Picture.PNG 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.202718.1571919183000.346.1571931360446%40Atlassian.JIRA.
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Mikhail Ianchikov commented on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task It looks like this: 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.202718.1571919183000.349.1571931600168%40Atlassian.JIRA.
[JIRA] (JENKINS-59840) NullPointerException when activating the plugin
Title: Message Title Oliver Gondža commented on JENKINS-59840 Re: NullPointerException when activating the plugin Thanks for the assert message. You are likely onto something. The config file path might have been accidentally changed during that migration causing your old config to break. That is certainly something to fix. The meaningless NPE you got is another thing to improve. When it comes to the dir opening dance, it is probably some spnego wizardry. 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.202575.157138872.351.1571931840229%40Atlassian.JIRA.
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Alex Earl commented on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task Hmmm, interesting. I'll try and figure out how to create a test that does this. 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.202718.1571919183000.353.1571933460552%40Atlassian.JIRA.
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Andrey Belyaevskiy commented on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task Oh=) it very easy. What we have: #14345, #14356 - 2 consecutive runs of our jobA - its our build job (build of c++ project) #9579 - first failed run of our jobB - its test job (runs some tests on build from jobA) We have little resources and our jobA takes much time (for our resources), so to make more builds (for further testing) I setup jobA - allow simultaneous builds (on different notes - with throttle concurrent build option enabled), not waiting for downstream job completion jobB - same settings While reading your comment I feel that issue can be in triggering jobB by 2 jobAs' runs but by the moment it was ok for us - except of issues with emailing in failure cases. Its ok for me to combine commiters of #14356 and #14357 to send them email to notify some brake tests. 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
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Andrey Belyaevskiy edited a comment on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task Oh=) it very easy.What we have: # #14345, #14356 - 2 consecutive runs of our jobA - its our build job (build of c++ project) # #9579 - first failed run of our jobB - its test job (runs some tests on build from jobA)We have little limited resources and our jobA takes much time (for our resources), so to make more builds (for further testing) I setup * jobA - allow simultaneous builds (on different notes nodes - with throttle concurrent build option enabled), not waiting for downstream job completion * jobB - same settingsWhile reading your comment I feel that issue can be in triggering jobB by 2 jobAs' runs but by the moment it was ok for us - except of issues with emailing in failure cases. Its ok for me to combine commiters of #14356 and #14357 to send them email to notify some brake tests. 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.202718.1571919183000.359.1571934480170%40Atlassian.JIRA.
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Andrey Belyaevskiy edited a comment on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task Oh=) it very easy.What we have: # #14345, #14356 - 2 consecutive runs of our jobA - its our build job (build of c++ project) # #9579 - first failed run of our jobB - its test job (runs some tests on build from jobA)We have limited resources and our jobA takes much time (for our resources), so to make more builds (for further testing) I setup * jobA - allow simultaneous builds (on different nodes - with throttle concurrent build option enabled), not waiting for downstream job completion * jobB - same settingsWhile reading your comment I feel that issue can be in triggering jobB by 2 jobAs' runs but by the moment it was ok for us - except of issues with emailing in failure cases. Its ok for me to combine commiters of #14356 and #14357 to send them email to notify some brake broke tests. 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.202718.1571919183000.362.1571934540169%40Atlassian.JIRA.
[JIRA] (JENKINS-59919) plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task
Title: Message Title Alex Earl commented on JENKINS-59919 Re: plugin takes developers for culprits only from first upstream build if build was triggered by more than one upstream task The issue I think is that I use context.getRun().getCause(Cause.UpstreamCause.class). This will return the first occurrence of the Cause.UpstreamCause instance in the causes list. This is most likely only going to be the first jobA. I may need to switch to Run.getCauses and loop over looking for all UpstreamCause instances. I'll play around with 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.202718.1571919183000.365.1571936280169%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black commented on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Peter Wein Jesse Glick would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this: node() { try { throw "error" } catch (err) { hudson.Functions.printThrowable(err) } } ?? I also found some good examples [here|https://code-maven.com/jenkins]. 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.182865.1497172331000.374.1571938080774%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
{code:java} {code} [~peddanet] [~jglick] would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this: {code:java} node() { try { throw "error" }catch (err) \ { hudson.Functions.printThrowable(err) } } {code }??I also found some good examples [here|[https://code-maven.com/jenkins]]. 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.182865.1497172331000.389.1571938380566%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
{code:java} {code} [~peddanet] [~jglick] would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this:{code:java}node() { try { throw "error" } catch (err) { hudson.Functions.printThrowable(err) } }{code}??I also found some good examples [here|[https://code-maven.com/jenkins]]. 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.182865.1497172331000.391.1571938380602%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
[~peddanet] [~jglick] would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this:{code:java}node() { try { throw "error" } catch (err) { hudson.Functions.printThrowable(err) } }{code}?? Is this function available in default (open source) installations of Jenkins? Do I need to also import anything to make this work?FWIW, I also found some good examples [here|[https://code-maven.com/jenkins]]. 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.182865.1497172331000.399.1571938440487%40Atlassian.JIRA.
[JIRA] (JENKINS-58936) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jell
Title: Message Title Timothy Harden commented on JENKINS-58936 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.189.jar!/jenkins/model/Jenkins/manage.jelly:46:53: Same issue, tried updating to 2.201 and updating all plugins and had no effect. Doesn't always happen in the same "Jelly" file: Manage Jenkins page it occurs inside the tag of the "Configure Global Security" link manage.jelly:86:80: java.lang.StackOverflowError On a Freestyle job main page it happens in the side panel after the "Configuration" task. actions.jelly:39:70: java.lang.StackOverflowError Tried backing up the ".jenkins" directory and doing a fresh install of 2.201 and that functioned but was of course missing all of my jobs, configuration, and plugins. 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.201280.1565796626000.429.1571939941028%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines The sleep 3 process was introduced when the heartbeat check feature was added in version 1.16 of durable-task, which translates to 2.18 of workflow-durable-task-step, which translates to 2.27 of workflow-job.Unless I missed a comment, it looks like the pipeline behaves as expected outside of "Terminated sleep 3" line.At least in [~parogui]’s [example|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=377961&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-377961], this might be a race condition between the sleep 3 process and when the script completes. Like [~dnusbaum] [mentioned earlier|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=362789&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-362789], the sleep 3 process is used to touch the output log file to show the script is still alive. However, when the script completes, it will write to a separate result file. A watcher service is checking for that result file every 100ms. Once that result file is found, results are transmitted and everything related to that specific step’s workspace is purged. It might be possible that the output file gets cleaned up right after the sleep 3 process checks if the file still exists, but before it gets touched again?There will be is a new release of durable-task (1.31) that will remove removes the sleep 3 process so this line won't pop up anymore. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-55308 intermittent "terminated" messages using sh in Pipelines Change By: Carroll Chiou Assignee: Devin Nusbaum Carroll Chiou 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.196395.1545434467000.486.1571941321036%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou started work on JENKINS-55308 Change By: Carroll Chiou Status: Open In Progress 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.196395.1545434467000.525.1571941503719%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Carroll Chiou edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines The sleep 3 process was introduced when the heartbeat check feature was added in version 1.16 of durable-task, which translates to 2.18 of workflow-durable-task-step, which translates to 2.27 of workflow-job.Unless I missed a comment, it looks like the pipeline behaves as expected outside of "Terminated sleep 3" line.At least in [~parogui]’s [example|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=377961&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-377961], this might be a race condition between the sleep 3 process and when the script completes. Like [~dnusbaum] [mentioned earlier|https://issues.jenkins-ci.org/browse/JENKINS-55308?focusedCommentId=362789&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-362789], the sleep 3 process is used to touch the output log file to show the script is still alive. However, when the script completes, it will write to a separate result file. A watcher service is checking for that result file every 100ms. Once that result file is found, results are transmitted and everything related to that specific step’s workspace is purged. It might be possible that the output file gets cleaned up right after the sleep 3 process checks if the file still exists, but before it gets touched again?There is a new release of durable-task (1.31) that removes the sleep 3 process so this line won't pop up anymore. Update: I have not been able to reproduce this issue, so I can't say for certain if this issue is resolved. Technically, it should, but it could be possible that the new version just changes the behavior of this bug. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Ramon Leon updated JENKINS-59844 Jenkins / JENKINS-59844 Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command Change By: Ramon Leon Resolution: Not A Defect Status: Fixed but Unreleased Reopened 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.202579.1571403818000.605.1571941980346%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Ramon Leon assigned an issue to Esther Álvarez Feijoo Jenkins / JENKINS-59844 Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command Change By: Ramon Leon Assignee: Ramon Leon Esther Álvarez Feijoo 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.202579.1571403818000.608.1571942040179%40Atlassian.JIRA.
[JIRA] (JENKINS-57829) podTemplate & container should not be marked advanced/deprecated
Title: Message Title Jesse Glick started work on JENKINS-57829 Change By: Jesse Glick Status: Open In Progress 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.199785.1559614844000.612.1571943420265%40Atlassian.JIRA.
[JIRA] (JENKINS-57829) podTemplate & container should not be marked advanced/deprecated
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-57829 podTemplate & container should not be marked advanced/deprecated Change By: Jesse Glick Assignee: Jesse Glick 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.199785.1559614844000.611.1571943420251%40Atlassian.JIRA.
[JIRA] (JENKINS-57828) podTemplate does not work well in Snippet Generator
Title: Message Title
Jesse Glick commented on JENKINS-57828
Re: podTemplate does not work well in Snippet Generator
Currently prints this mess:
podTemplate(inheritFrom: '', instanceCap: 0, namespace: '', nodeSelector: '', podRetention: always(), serviceAccount: '', workspaceVolume: dynamicPVC(accessModes: 'ReadWriteOnce', requestsSize: '', storageClassName: ''), yaml: '') {
// some block
}
Cleaned-up behavior should be verified with SnippetizerTester.
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.199784.1559614502000.610.1571943420205%40Atlassian.JIRA.
[JIRA] (JENKINS-57829) podTemplate & container should not be marked advanced/deprecated
Title: Message Title Jesse Glick updated JENKINS-57829 Jenkins / JENKINS-57829 podTemplate & container should not be marked advanced/deprecated Change By: Jesse Glick Status: In Progress Review 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.199785.1559614844000.613.1571943480107%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Jesper Andersson updated an issue Jenkins / JENKINS-59903 durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Change By: Jesper Andersson Environment: Centos 7.7Jenkins ver. 2.190.1 (installed by yum , not in container )Durable Task Plugin v. 1.31 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.202653.1571840997000.628.1571945700939%40Atlassian.JIRA.
[JIRA] (JENKINS-59923) Repo Manifest action clashes with the built in Tags action
Title: Message Title Simon Williams updated JENKINS-59923 Jenkins / JENKINS-59923 Repo Manifest action clashes with the built in Tags action Change By: Simon Williams Status: In Progress Review 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.202722.1571927424000.644.1571946120259%40Atlassian.JIRA.
[JIRA] (JENKINS-59923) Repo Manifest action clashes with the built in Tags action
Title: Message Title Simon Williams commented on JENKINS-59923 Re: Repo Manifest action clashes with the built in Tags action Created pull request on jenkinsci/repo-plugin repository: https://github.com/jenkinsci/repo-plugin/pull/57 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.202722.1571927424000.643.1571946120230%40Atlassian.JIRA.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Simon Williams commented on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 I have added a pull request to the jenkinsci/repo-plugin repository to work around this issue: https://github.com/jenkinsci/repo-plugin/pull/56 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.199890.1560007155000.647.1571946180468%40Atlassian.JIRA.
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Constantin Bugneac commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Getting similar exceptions in the log: Oct 24, 2019 8:32:17 PM WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFileAvoid calling getLogFile on build-packer #8 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1088) at org.jenkinsci.plugins.compressbuildlog.BuildLogCompressor$CompressBuildlogRunListener.onFinalized(BuildLogCompressor.java:85) at hudson.model.listeners.RunListener.fireFinalized(RunListener.java:255) at hudson.model.Run.onEndBuilding(Run.java:2000) at org.jenkinsci.plugins.workflow.job.WorkflowRun.finish(WorkflowRun.java:612) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$800(WorkflowRun.java:133) at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:999) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.notifyListeners(CpsFlowExecution.java:1463) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$3.run(CpsThreadGroup.java:458) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:37) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Oct 24, 2019 8:34:35 PM INFO hudson.model.AsyncPeriodicWork$1 run Jenkins version: 2.201 I don't have groovy-postbuild plugin installed. Plugin versions. docker-workflow 1.21 workflow-aggregator 2.6 workflow-api 2.37 workflow-basic-steps 2.18 workflow-cps 2.74 workflow-cps-global-lib 2.15 workflow-durable-task-step 2.34 workflow-job 2.35 workflow-multibranch 2.21 workflow-remote-loader 1.5 workflow-scm-step 2.9 workflow-step-api 2.20 workflow-support 3.3 Any help would much appreciated.
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keeps on posting the Build Started comment without build result
Title: Message Title Nareen M updated JENKINS-59851 Duplicates JENKINS-59833. Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keeps on posting the Build Started comment without build result Change By: Nareen M Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/releases/tag/stash-pullrequest-builder-1.14 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keeps on posting the Build Started comment without build result
Title: Message Title Nareen M updated JENKINS-59851 Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keeps on posting the Build Started comment without build result Change By: Nareen M Status: Fixed but Unreleased Resolved 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.202587.1571422014000.683.1571947020219%40Atlassian.JIRA.
[JIRA] (JENKINS-32898) Disable Strict Forbidden File Verification option always causes trigger
Title: Message Title Ripudaman Flora commented on JENKINS-32898 Re: Disable Strict Forbidden File Verification option always causes trigger I followed exact same steps where: Forbidden file – path – script/** Forbidden file – path – /COMMIT_MSG I also checked "Disable Strict Forbidden File Verification" But it still triggers the build, I am expecting it should not trigger the build if it matches the file in the path specified. The file is under "scripts/blah.sh" I won't be able to share the data since it is work-related but I can try to reproduce it on my local environment. I would like to know if it is working as expected though. 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.168096.1455206485000.686.1571948280322%40Atlassian.JIRA.
[JIRA] (JENKINS-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title Constantin Bugneac commented on JENKINS-49710 Re: Pipelines run under heavy load sometimes hang running Docker I'm experiencing the same issue sporadically. 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.188649.1519376534000.695.1571949240179%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Moshe Zvi updated JENKINS-59892 Jenkins / JENKINS-59892 Token evaluation fails in GitPlugin Change By: Moshe Zvi Status: In Review Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202637.1571767379000.698.1571950560317%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Constantin Bugneac commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Having the same issue with the 1.31 version of durable-task plugin. Had to rollback to 1.30. 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.202653.1571840997000.701.1571950920409%40Atlassian.JIRA.
[JIRA] (JENKINS-59926) EnvInject of properties file fails on some slaves
Title: Message Title Moshe Zvi created an issue Jenkins / JENKINS-59926 EnvInject of properties file fails on some slaves Issue Type: Bug Assignee: Unassigned Attachments: envinject.zip Components: envinject-plugin Created: 2019-10-24 21:17 Environment: Jenkins 2.190.1 (also in 2.176.1) EnvInject plugin 2.3.0 (also in 2.2.1) Priority: Critical Reporter: Moshe Zvi This relates to JENKINS-59892, but I've managed to narrow it down. The same job was run on two identical slaves. the job writes a property to a file, injects the file, and then attempts to echo it. On one slave this succeeds, on another it fails. This is killing our system - many jobs fail due to missing attributes. I've attached all the configuration files i could think of in the zip. Add Comment
[JIRA] (JENKINS-59926) EnvInject of properties file fails on some slaves
Title: Message Title Moshe Zvi updated an issue Jenkins / JENKINS-59926 EnvInject of properties file fails on some slaves Change By: Moshe Zvi This relates to JENKINS-59892, but I've managed to narrow it down. The same job was run on two identical slaves. the job writes a property to a file, injects the file, and then attempts to echo it. On one slave this succeeds, on another it fails. This is killing our system - many jobs fail due to missing attributes. I've attached all the configuration files i could think of in the zip. Note:As a comparison, I also tried injecting a variable not from a file - that succeeds in both (see VAR_IN_FILE vs. VAR_IN_CONTENT in the injectedEnvVars files). 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 discu
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Mark Waite commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Constantin Bugneac that seems to be a call reading the log file from org.jenkinsci.plugins.compressbuildlog, the compress build log plugin, probably at line 85. You're welcome to submit a pull request to that repository proposing to correct that plugin. Alternately, you could disable build log compression in your job definitions. 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.194755.1539777336000.739.1571952180780%40Atlassian.JIRA.
[JIRA] (JENKINS-59926) EnvInject of properties file fails on some slaves
Title: Message Title Moshe Zvi updated an issue Jenkins / JENKINS-59926 EnvInject of properties file fails on some slaves Change By: Moshe Zvi This relates to JENKINS-59892, but I've managed to narrow it down. The same job was run on two identical slaves. the job writes a property to a file, injects the file, and then attempts to echo it. On one slave this succeeds, on another it fails. This is killing our system - many jobs fail due to missing attributes. I've attached all the configuration files i could think of in the zip. Note:As a comparison, I also tried injecting a variable not from a file - that succeeds in both (see VAR_IN_FILE vs. VAR_IN_CONTENT in the injectedEnvVars files). Additional info:I tried using a full path (as opposed to a partial path) and it seems to work (e.g. $WORKSPACE/build.properties vs. build.properties). 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
[JIRA] (JENKINS-59927) Test Result Trend / show test # and failure # are unhelpful
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59927 Test Result Trend / show test # and failure # are unhelpful Issue Type: Improvement Assignee: Unassigned Components: junit-plugin Created: 2019-10-24 21:36 Priority: Minor Reporter: Josh Soref We have a project which has approximately 2500 tests which are run in an average build. For a given run, between 0 and 3 tests may fail (on average, 0). The default view "Test Result Trend" shows a blue graph of all of our passing tests – the scale of the failing tests is invisible. This makes the default view absolutely useless. As it happens, the number of tests we run in a given run actually fluctuates significantly (50 one run, 1900 the next). To make the graphs useful for us, a couple of presentations could be considered: Just show two graphs side by side. – Personally, I don't think this is a great approach. Use independent Y axes (typically a left axis for the total tests, and a right axis for failed tests) – this is fairly common in charts with mismatched scales. – In this model, the left y-axis label could be tests and the right y-axis label could be failures. Use an inverted graph for failures and stack them so that they share a common x-axis but total tests counts grow up, and failed tests grow down from the common x-axis (with independently labeled y-axes on the left). Beyond that: The label for the link to change the view show test # and failure # isn't really a great link text, it's both fairly long and annoyingly terse at the same time.
[JIRA] (JENKINS-54998) Stash and archive should refuse symlinks
Title: Message Title Chris Dore commented on JENKINS-54998 Re: Stash and archive should refuse symlinks Jesse Glick why should a symlink be an error? Since symlinks are not preserved, we abandoned using stash and instead we are now allocating a node for the entire pipeline, even when that node could be released back to the pool during certain stages. I would love to revisit our workaround and improve node utilization, having stash handle symlinks would make this very easy. Are there other alternative ideas to allow a pipeline to save state containing symlinks across stages on different nodes/workspaces? 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.196033.1543911929000.751.1571953740137%40Atlassian.JIRA.
[JIRA] (JENKINS-59928) Add first and last build buttons to blueocean
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59928 Add first and last build buttons to blueocean Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-10-24 21:52 Priority: Minor Reporter: Josh Soref JENKINS-49827 added Next/Previous buttons. I think the right iconography is |< and >| for first/last. There may be some value to have << and >> for jumping back/forward some number of builds (5 or 10 at a time?). Add Comment This message was s
[JIRA] (JENKINS-54128) Deprecated calls to Run.getLogFile
Title: Message Title Constantin Bugneac commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile Thank you Mark. 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.194755.1539777336000.775.1571954520763%40Atlassian.JIRA.
[JIRA] (JENKINS-59929) blueocean should indicate when a PR is closed
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59929 blueocean should indicate when a PR is closed Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin, github-branch-source-plugin Created: 2019-10-24 22:09 Priority: Minor Reporter: Josh Soref (blueocean-dashboard) I can't quite describe what's going on. Open pull requests generally show: https://github.com/jenkinsci/blueocean-plugin/blob/3aca1b85452de1ceba39d86f318efb42ce03cc26/blueocean-dashboard/src/main/js/components/RunDetailsHeader.jsx#L146 Sometimes, closed PRs don't seem to show this. It's possible that I'm in the wrong view. Sometimes, closed PRs do show this, but it would be more helpful if it could indicate that the PR is closed (yes, I can click the link, but it's an expensive operation for a user, whereas the information would be more valuable displayed directly to the user in blue ocean). Add Comment
[JIRA] (JENKINS-59929) blueocean should indicate when a PR is closed
Title: Message Title Josh Soref commented on JENKINS-59929 Re: blueocean should indicate when a PR is closed Oddly, when I'm starting from the Pull Requests tab of blue ocean, things tend not to have the PR pop out link... 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.202730.1571954987000.777.1571955120071%40Atlassian.JIRA.
