[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite My FreeNAS 11.3.U1 server hosts a FreeNAS 10 based jail that runs a git server. The platformlabeler on that jail reports 11.3 (the kernel version) instead of 10 (the version of the operating system environment). It should report the version of utilities in the jail, not the version of the FreeBSD kernel that is hosting the jail.The platformlabeler should report the version of the utilities in the jail (FreeNAS 10 in this case) to be consistent with Docker containers. In a Docker container, the operating system is reported based on the utilities running the operating system (/etc/os-release), not based on the operating system hosting the container. Since most uses of a platform label tend to be connected to the versions of the utilities on the operating system rather than the kernel, users will prefer to have the generated labels match the utilities more than the kernel. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Issue Type: Improvement Assignee: lifeless Components: platformlabeler-plugin Created: 2020-03-20 03:48 Environment: Platformlabeler 5.4 FreeBSD jail running on OS version different than the FreeBSD kernel Priority: Minor Reporter: Mark Waite My FreeNAS 11.3.U1 server hosts a FreeNAS 10 based jail that runs a git server. The platformlabeler on that jail reports 11.3 (the kernel version) instead of 10 (the version of the operating system environment). It should report the version of utilities in the jail, not the version of the FreeBSD kernel that is hosting the jail. The platformlabeler should report the version of the utilities in the jail (FreeNAS 10 in this case) to be consistent with Docker containers. In a Docker container, the operating system is reported based on the utilities running the operating system (/etc/os-release), not based on the operating system hosting the container. Add
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Luke Lussenden commented on JENKINS-43820 Re: Stage name must be a string literal I would also appreciate support for constants. My use-case involves shared library code which makes post action decisions based on the failed stage name. Re-defining the stage name in multiple places is brittle and someone could easily decide to change the display name causing code to silently fail when the stage name doesn't match what it's looking for. Using a constant would help this problem. Support for: static final String BUILD = "Build Stage" For stage names would be most appreciated. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.9829.1584665820629%40Atlassian.JIRA.
[JIRA] (JENKINS-61514) Jenkins not recognizing git option.
Title: Message Title Mark Waite resolved as Cannot Reproduce Jenkins / JENKINS-61514 Jenkins not recognizing git option. Change By: Mark Waite Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205209.1584554554000.9827.1584665700199%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan commented on JENKINS-61509 Re: Release Notes field is not interpolating values from Variable Hi Jose Salgado. Very interesting. Let me ask you one question. Where in your freestyle configuration are you specifying the release notes environment variable? I was able to recreate your issue. but partially. I've added an execute shell step before the AppCenter step and it doesn't get interpolated.However when I use another environment variable it does get correctly interpolated. This Stackoverflow post suggests that you can't pass environment variables in this way and that you need a different plugin to do that. Is it possible that this is what is happening in your case? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.9824.1584663960179%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61509 Release Notes field is not interpolating values from Variable Change By: Mez Pahlan Attachment: appcenter-console.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.9821.1584663780200%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61509 Release Notes field is not interpolating values from Variable Change By: Mez Pahlan Attachment: appcenter-release-notes.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.9818.1584663720206%40Atlassian.JIRA.
[JIRA] (JENKINS-61509) Release Notes field is not interpolating values from Variable
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61509 Release Notes field is not interpolating values from Variable Change By: Mez Pahlan Attachment: execute-shell-step.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205204.1584544055000.9816.1584663660208%40Atlassian.JIRA.
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verfies ostname in SSL certificate
Title: Message Title Szymon S commented on JENKINS-61596 Re: http client in jenkins swarm badly verfies ostname in SSL certificate I see httpclient 4.5.12 is already pulled in https://github.com/jenkinsci/swarm-plugin/commit/bd01dc3ae4918bfa77730ad05745232f665a7e96 How soon do you plan new release? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205293.1584662414000.9813.1584662820050%40Atlassian.JIRA.
[JIRA] (JENKINS-61596) http client in jenkins swarm badly verfies ostname in SSL certificate
Title: Message Title Szymon S created an issue Jenkins / JENKINS-61596 http client in jenkins swarm badly verfies ostname in SSL certificate Issue Type: Bug Assignee: Unassigned Components: swarm-plugin Created: 2020-03-20 00:00 Environment: Jenkins ver. 2.204.5 swarm 3.18 Labels: regression SSL Priority: Major Reporter: Szymon S javax.net.ssl.SSLPeerUnverifiedException: Certificate for doesn't match any of the subject alternative names: [jenkins.xx.yy, other_name.xx.yy] at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:507) at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437) at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384) at shaded.org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) at shaded.org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) at shaded.org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) at shaded.org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at
[JIRA] (JENKINS-60194) Separate injector for test resources
Title: Message Title Mez Pahlan assigned an issue to Unassigned Jenkins / JENKINS-60194 Separate injector for test resources Change By: Mez Pahlan Assignee: Mez Pahlan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203164.1574069472000.9795.1584662040670%40Atlassian.JIRA.
[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title Mez Pahlan assigned an issue to Unassigned Jenkins / JENKINS-61337 Debug Symbols uploads > 256meg refused. Change By: Mez Pahlan Assignee: Mez Pahlan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204924.1583357801000.9776.1584661980758%40Atlassian.JIRA.
[JIRA] (JENKINS-61369) Symbol file upload needs improvements
Title: Message Title Mez Pahlan assigned an issue to Unassigned Jenkins / JENKINS-61369 Symbol file upload needs improvements Change By: Mez Pahlan Assignee: Mez Pahlan Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205022.1583507625000.9778.1584661980822%40Atlassian.JIRA.
[JIRA] (JENKINS-61595) checkApiToken - NullPointerException
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61595 checkApiToken - NullPointerException Issue Type: Bug Assignee: Anatoliy Varanitsa Components: ecs-publisher-plugin Created: 2020-03-19 23:52 Priority: Minor Reporter: Josh Soref 2020-03-19 23:21:40.400+ [id=25]WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://localhost:9000/descriptorByName/de.eacg.ecs.publisher.PublisherCredentials/checkApiToken java.lang.NullPointerException at de.eacg.ecs.publisher.PublisherCredentials$DescriptorImpl.doCheckApiToken(PublisherCredentials.java:156) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:485) ... 2020-03-19 23:21:40.402+ [id=25]WARNING h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID 52f18e9c-a099-4612-a49f-a2fc2c840d53 java.lang.NullPointerException at de.eacg.ecs.publisher.PublisherCredentials$DescriptorImpl.doCheckApiToken(PublisherCredentials.java:156) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:485) Caused: javax.servlet.ServletException 23:21:44.473+ [id=27]WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving http://localhost:9000/descriptorByName/de.eacg.ecs.publisher.PublisherCredentials/checkApiToken java.lang.NullPointerException at de.eacg.ecs.publisher.PublisherCredentials$DescriptorImpl.doCheckApiToken(PublisherCredentials.java:156) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:485) Caused: java.lang.reflect.InvocationTargetException 2020-03-19 23:21:44.474+ [id=27]WARNING h.i.i.InstallUncaughtExceptionHandler#handleException: Caught unhandled exception with ID d3c40adc-b883-436e-b05f-bea8f26e4204 java.lang.NullPointerException
[JIRA] (JENKINS-59376) Return warning directly from validator
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-59376 Return warning directly from validator Change By: Mez Pahlan Priority: Minor Trivial Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201932.1568494744000.9788.1584661980970%40Atlassian.JIRA.
[JIRA] (JENKINS-61369) Symbol file upload needs improvements
Title: Message Title Mez Pahlan commented on JENKINS-61369 Re: Symbol file upload needs improvements Hi Claus Chierici can you post your configuration for the AppCenter plugin please. Also can you post the build output from Jenkins for a build that you think isn't working correctly. What you've described is exactly how we are uploading Android mapping files. For symbols we check what platform your main app upload is for. For Android what you described regarding the versionName and versionCode is exactly what we have always done. I have no idea where "upload-.zip" is coming from. Can you point out in the plugin code where you think this is coming from? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205022.1583507625000.9774.1584661920115%40Atlassian.JIRA.
[JIRA] (JENKINS-61369) Symbol file upload needs improvements
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61369 Symbol file upload needs improvements Change By: Mez Pahlan Priority: Major Trivial Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205022.1583507625000.9764.1584661380189%40Atlassian.JIRA.
[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61337 Debug Symbols uploads > 256meg refused. Change By: Mez Pahlan Labels: help-wanted Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204924.1583357801000.9762.1584660900399%40Atlassian.JIRA.
[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title Mez Pahlan updated an issue Jenkins / JENKINS-61337 Debug Symbols uploads > 256meg refused. Change By: Mez Pahlan Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204924.1583357801000.9760.1584660900341%40Atlassian.JIRA.
[JIRA] (JENKINS-61337) Debug Symbols uploads > 256meg refused.
Title: Message Title Mez Pahlan commented on JENKINS-61337 Re: Debug Symbols uploads > 256meg refused. Sorry for the late reply on this. I can't figure out how to get this to work by side stepping the official APIs. I'll happily take a PR if anyone can figure this out however if it isn't in the official API docs I don't have the bandwidth to look into it at the moment. Apologies. If it helps anyone what we currently do here is inline with the link above in three API requests. 1) request an upload url for the symbols 2) upload to this url 3) commit this upload. From Terry's investigation there may be a way to reverse engineer what the node plugin is doing which looks to being in the same way as we do by requesting an upload url but instead of directly uploading to it then uses Azure Blob Storage. There looks to be a Java SDK for Azure Blob Storage which might be worth investigating. For reference here is what the node plugin is doing its thing. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204924.1583357801000.9758.1584660840133%40Atlassian.JIRA.
[JIRA] (JENKINS-59462) Support release notes from file
Title: Message Title Mez Pahlan commented on JENKINS-59462 Re: Support release notes from file There'll be a new field called pathToReleaseNotes that will be merged with releaseNotes up to a merged limit of 5000 characters in the next update. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202059.1568976886000.9748.1584658264191%40Atlassian.JIRA.
[JIRA] (JENKINS-59462) Support release notes from file
Title: Message Title Mez Pahlan updated JENKINS-59462 Jenkins / JENKINS-59462 Support release notes from file Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202059.1568976886000.9752.1584658264261%40Atlassian.JIRA.
[JIRA] (JENKINS-59462) Support release notes from file
Title: Message Title Mez Pahlan updated JENKINS-59462 Jenkins / JENKINS-59462 Support release notes from file Change By: Mez Pahlan Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202059.1568976886000.9754.1584658264290%40Atlassian.JIRA.
[JIRA] (JENKINS-61594) Getting exception when running Micro Focus Plugin for Performance Center Git Integration
Title: Message Title Chris Simon created an issue Jenkins / JENKINS-61594 Getting exception when running Micro Focus Plugin for Performance Center Git Integration Issue Type: Bug Assignee: Daniel Danan Components: hp-application-automation-tools-plugin Created: 2020-03-19 20:36 Environment: Jenkins Version: 2.138.3 Plugin Used: micro-focus-performance-center-integration Version 1.1.2 specific plugin name "Synchronize Performance Center With Git" Perf Center Server (12.63) OS: Windows Server 2012 R2 openjdk version: 1.8.0_242 OpenJDK Runtime Env: Corretto-8.242.07.1 (build 1.8.0_242-b07) ALM Server (12.60) OS: Windows Server 2012 R2 openjdk version: 1.8.0_242 OpenJDK Runtime Env: Corretto-8.242.07.1 (build 1.8.0_242-b07) Gitlab Enterprise Edition 12.4.1-eeBrowser Used: Chrome Priority: Major Reporter: Chris Simon Getting a general exception when trying to use the sync git with performance center plugin in Jenkins. This is related to another issue I opened. In the previous environment, the plugin worked. But now I am in a different Jenkins environment and I am getting this exception. Could you please advise as to what may be causing it? Thu 2020 Mar 19 at 16:01:26.203 PM EDT - Performance Center version 12.60 or above detected. * Uploading scripts * Each script folder will be automatically compressed in the workspace and then uploaded to the Performance Center project: Thu 2020 Mar 19 at 16:01:26.210 PM EDT - General exception: null. Thu 2020 Mar 19 at 16:01:26.273 PM EDT - Logout: succeeded Build
[JIRA] (JENKINS-61593) Several Warnings-ng plugin tokens do not work
Title: Message Title Edwin Shen created an issue Jenkins / JENKINS-61593 Several Warnings-ng plugin tokens do not work Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2020-03-19-16-13-33-498.png Components: warnings-ng-plugin Created: 2020-03-19 20:15 Labels: plugin Priority: Minor Reporter: Edwin Shen It seems that TOTAL_NORMAL and TOTAL_LOW do not work. However, other tokens like NEW_HIGH, NEW_NORMAL, NEW_LOW, TOTAL_HIGH do work. Example of token not working below. Add Comment
[JIRA] (JENKINS-61411) No build status information is sent to bitbucket when using pipeline job with script
Title: Message Title Daniel Kjellin updated JENKINS-61411 Jenkins / JENKINS-61411 No build status information is sent to bitbucket when using pipeline job with script Change By: Daniel Kjellin Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205065.1583829601000.9714.1584648900227%40Atlassian.JIRA.
[JIRA] (JENKINS-61589) role-strategy-plugin does not respect distributed lists
Title: Message Title Tobias Honacker commented on JENKINS-61589 Re: role-strategy-plugin does not respect distributed lists Oleg Nenashev Thanks. The DL we assigned to roles is listed in the /whoAmI page of the users. What should I restart? Jenkins? We already did that many times. The problem exists since we installed the plugin in October 2019. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205286.1584631779000.9702.1584642180498%40Atlassian.JIRA.
[JIRA] (JENKINS-61592) Enable auto refresh button os missing
Title: Message Title Thomas Hauser created an issue Jenkins / JENKINS-61592 Enable auto refresh button os missing Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2020-03-19 16:53 Environment: Jenkins Version 2.225 Labels: memory-leak auto-refresh Priority: Major Reporter: Thomas Hauser The enable auto refresh button has been missing since the last update. Without this function there is a memory problem on our server. Add Comment
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title
Alex Taylor updated an issue
Jenkins / JENKINS-61591
Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Change By:
Alex Taylor
Issue:In declarative when you have a series of stages with one action outside of those stages that fails, it will cause the stage view status (the blue/red ball on the left side of the view) to show the incorrect status of the build.Steps to reproduce:Create a pipeline with this as the definition:{code:java}pipeline {agent any checkoutstages {stage('Build') { steps { echo "hello"}}stage('Test') { steps { echo "hello"}}stage('Deploy') { steps { echo "hello"}}}}{code}Run that code and look at the stage view to see that it appears the build was successful but it clearly failed on the build status screen on the left. Build 203 looks correct and build 204 is the one with the incorrect status indicator: !Screen Shot 2020-03-19 at 12.43.38 PM.png|thumbnail! Expected results:The stage view page correctly shows the build status being failed.The biggest issue with this is that if a build fails to checkout its Jenkinsfile it will do this same thing which causes a problem where the build looks successful when it actually wasn't
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-61591 Using Stage view with mixed in/out of stage actions causes the build status to be wrong Change By: Alex Taylor Attachment: Screen Shot 2020-03-19 at 12.43.38 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205288.1584636193000.9685.1584636300325%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-61591
Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Issue Type:
Bug
Assignee:
Sam Van Oort
Components:
pipeline-stage-view-plugin
Created:
2020-03-19 16:43
Priority:
Minor
Reporter:
Alex Taylor
Issue: In declarative when you have a series of stages with one action outside of those stages that fails, it will cause the stage view status (the blue/red ball on the left side of the view) to show the incorrect status of the build. Steps to reproduce: Create a pipeline with this as the definition:
pipeline {
agent any
checkout
stages {
stage('Build') {
steps {
echo "hello"
}
}
stage('Test') {
steps {
echo "hello"
}
}
stage('Deploy') {
steps {
echo "hello"
}
}
}
}
Run that code and look at the stage view to see that it appears the build was successful but it clearly failed on the build status screen on the left. Expected results: The stage view page correctly shows the build status being failed. The biggest issue with this is that if a build fails to checkout its Jenkinsfile it will do this same thing which causes a problem where the build looks successful when it actually wasn't
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title
Markus Schenkel edited a comment on JENKINS-60299
Re: Make build description in build history widget configurable or possible to hide
Sorry, but I did not read "maintenance issues" as "deprecated". also the mobile version does not show the banner at all. Also the banner does not appear at all on the mobile version. Any idea why it can not be changed through the script console using{code:java}System.setProperty("historyWidget.descriptionLimit", "-1") // also tried 0println SystemProperties.getInteger("historyWidget.descriptionLimit") // value does change to -{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.9673.1584635460294%40Atlassian.JIRA.
[JIRA] (JENKINS-61590) RebuildCause should not inherit from UpstreamCause
Title: Message Title
Roman Donchenko updated an issue
Jenkins / JENKINS-61590
RebuildCause should not inherit from UpstreamCause
Change By:
Roman Donchenko
Currently, [{{RebuildCause}}|https://github.com/jenkinsci/rebuild-plugin/blob/rebuild-1.31/src/main/java/com/sonyericsson/rebuild/RebuildCause.java] inherits from {{Cause.UpstreamCause}}. This causes several problems:* {{currentBuild.upstreamBuilds}} includes the build that the current build was rebuilt from, even though that's not actually an upstream build.* In downstream jobs of a rebuilt job, the {{RebuildCause}} gets transformed into a plain {{UpstreamCause}} due to [ Cause UpstreamCause .trim|https://github.com/jenkinsci/jenkins/blob/jenkins-2.226/core/src/main/java/hudson/model/Cause.java#L232], which makes it impossible to distinguish a child of a rebuild job from a grandchild of the original job.It would be nice if this was fixed in some way, either by making {{RebuildCause}} not inherit from {{UpstreamCause}} or maybe, if compatibility constraints make that impossible, by introducing a new rebuild cause class.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61590) RebuildCause should not inherit from UpstreamCause
Title: Message Title Roman Donchenko created an issue Jenkins / JENKINS-61590 RebuildCause should not inherit from UpstreamCause Issue Type: Improvement Assignee: ragesh_nair Components: rebuild-plugin Created: 2020-03-19 16:28 Priority: Minor Reporter: Roman Donchenko Currently, RebuildCause inherits from Cause.UpstreamCause. This causes several problems: currentBuild.upstreamBuilds includes the build that the current build was rebuilt from, even though that's not actually an upstream build. In downstream jobs of a rebuilt job, the RebuildCause gets transformed into a plain UpstreamCause due to Cause.trim, which makes it impossible to distinguish a child of a rebuild job from a grandchild of the original job. It would be nice if this was fixed in some way, either by making RebuildCause not inherit from UpstreamCause or maybe, if compatibility constraints make that impossible, by introducing a new rebuild cause class. Add Comment
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title Damian Jesionek commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin I added a PR that fixes this issue on github. Please review carefully as this is my first contribution to a jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.9580.1584635101538%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Steven Gardell commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script This same behavior is seen with scripted pipelines and it can be worked around - with increased pain as the functional complexity of a pipeline grows. Does anyone have any insight as to whether this is a core groovy or java limitation? Rather than spending a ton of time working around this it would be really nice just to make the limit 10 times as big... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.9584.1584635101581%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61280 Allow dynamic stage names Change By: Stefan Drissen Attachment: image-2020-03-19-17-20-50-002.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.9577.1584635040183%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Stefan Drissen commented on JENKINS-61280 Re: Allow dynamic stage names I'm revisiting replacing a big xml template based multi-job project with a declarative matrix pipeline. While the matrix implementation was really nice and quick to setup, the visualization was a bit of let down. Dynamic stage names would really really really help. Current state: With stage names based on matrix values: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.9574.1584634980454%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61280 Allow dynamic stage names Change By: Stefan Drissen Attachment: image-2020-03-19-17-22-05-861.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.9571.1584634980409%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) I've already provided all the directions I know about how to downgrade. You have to manually download the old version of the plugin from the link provided in my earlier comment, and then you can upload the file following these directions: https://jenkins.io/doc/book/managing/plugins/#from-the-web-ui-2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.9568.1584634920167%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61280 Allow dynamic stage names Change By: Stefan Drissen Attachment: image-2020-03-19-17-20-50-002.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.9566.1584634860770%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61280 Allow dynamic stage names Change By: Stefan Drissen Attachment: image-2020-03-19-17-20-23-015.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.9563.1584634860729%40Atlassian.JIRA.
[JIRA] (JENKINS-28382) workflow plugin: no opton to "Wipe Out Current Workspace"
Title: Message Title Jesse Glick commented on JENKINS-28382 Re: workflow plugin: no opton to "Wipe Out Current Workspace" That is one of the enhancements listed in JENKINS-26138. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162818.1431535967000.9556.1584634680201%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Thanks for the update and escalating with your team. Can you possibly send me some directions on how to install the old HPI file from the plugin manager page? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.9554.1584634560195%40Atlassian.JIRA.
[JIRA] (JENKINS-61589) role-strategy-plugin does not respect distributed lists
Title: Message Title Oleg Nenashev commented on JENKINS-61589 Re: role-strategy-plugin does not respect distributed lists My guess is that the Active Directory plugin does not properly list authorities in the distributed lists. It can be checked by going to the /whoAmI page for users who are supposed to have permissions. Also, there are some permission caching issues reported for recent weekly releases. I still need to investigate them, but it would be great if you could check whether the issue remains after the restrt Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205286.1584631779000.9552.1584634500131%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Daniel Beck commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Startup-only system property. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.9545.1584634260312%40Atlassian.JIRA.
[JIRA] (JENKINS-28382) workflow plugin: no opton to "Wipe Out Current Workspace"
Title: Message Title Tim Black edited a comment on JENKINS-28382 Re: workflow plugin: no opton to "Wipe Out Current Workspace" I don't see how this issue duplicates JENKINS-26138 Support workspaces for Pipeline jobs.I would like the ability to get the "Workspaces" --> "Wipe Out Current Workspace" option in the UI. I'm using Jenkins v2.190.3. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162818.1431535967000.9539.1584634080287%40Atlassian.JIRA.
[JIRA] (JENKINS-61589) role-strategy-plugin does not respect distributed lists
Title: Message Title Tobias Honacker updated an issue Jenkins / JENKINS-61589 role-strategy-plugin does not respect distributed lists Change By: Tobias Honacker Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205286.1584631779000.9536.1584632340216%40Atlassian.JIRA.
[JIRA] (JENKINS-61589) role-strategy-plugin does not respect distributed lists
Title: Message Title Tobias Honacker created an issue Jenkins / JENKINS-61589 role-strategy-plugin does not respect distributed lists Issue Type: Bug Assignee: Oleg Nenashev Attachments: Screenshot.jpg Components: role-strategy-plugin Created: 2020-03-19 15:29 Environment: Jenkins ver. 2.225 openjdk version 1.8.0_242 role-strategy-plugin 2.16 Linux Ubuntu 16.04 Priority: Minor Reporter: Tobias Honacker Hi, we are trying to get the role-strategy-plugin working without success using distributed lists. Assigning item roles to a DL is working but the user inside the DL does not receive any permissions. Assigning a single user is working so the pattern works but does not make sense because we have a lot of users. The DL is listed with a group symbol so my guess is that AD is working in my eyes so no problems here. Is someone else having this problem? Thanks and best regards Tobias
[JIRA] (JENKINS-61588) Failed to convert API response to XML: INVALID_CHARACTER_ERR
Title: Message Title yassir bonyad updated an issue Jenkins / JENKINS-61588 Failed to convert API response to XML: INVALID_CHARACTER_ERR Change By: yassir bonyad Hi,im using :zap- version : 2.8.1zap- plugin 1.1.0 : [https://plugins.jenkins.io/zap]Jenkins version : 2.204.5 im using zap script-based-authentication. After the script is loaded in jenkins i got following exception. See attachment.[^error.txt] Is this a bug inside the plugin ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205285.1584627511000.9532.1584629340146%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title
Markus Schenkel commented on JENKINS-60299
Re: Make build description in build history widget configurable or possible to hide
Sorry, but I did not read "maintenance issues" as "deprecated". also the mobile version does not show the banner at all. Also the banner does not appear at all on the mobile version. Any idea why it can not be changed through the script console using
System.setProperty("historyWidget.descriptionLimit", "-1") // also tried 0
println SystemProperties.getInteger("historyWidget.descriptionLimit") // value does change to -
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.9530.1584629100282%40Atlassian.JIRA.
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title Jesse Glick commented on JENKINS-52750 Re: dir step creates a @tmp directory at level. Do not use dir for this purpose. Simply start your sh script with cd /opt/tools. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192646.1532606916000.9515.1584629040250%40Atlassian.JIRA.
[JIRA] (JENKINS-61588) Failed to convert API response to XML: INVALID_CHARACTER_ERR
Title: Message Title yassir bonyad updated an issue Jenkins / JENKINS-61588 Failed to convert API response to XML: INVALID_CHARACTER_ERR Change By: yassir bonyad Labels: zap zap-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205285.1584627511000.9503.1584627600161%40Atlassian.JIRA.
[JIRA] (JENKINS-61588) Failed to convert API response to XML: INVALID_CHARACTER_ERR
Title: Message Title yassir bonyad created an issue Jenkins / JENKINS-61588 Failed to convert API response to XML: INVALID_CHARACTER_ERR Issue Type: Bug Assignee: Goran Sarenkapa Attachments: error.txt Components: zap-plugin Created: 2020-03-19 14:18 Priority: Minor Reporter: yassir bonyad Hi, im using : zap-plugin 1.1.0 : https://plugins.jenkins.io/zap Jenkins version : 2.204.5 im using zap script-based-authentication. After the script is loaded in jenkins i got following exception. See attachment. error.txt Is this a bug inside the plugin ? Add Comment
[JIRA] (JENKINS-61388) jiraGetFields: "Illegal base64 character" since 1.5.2
Title: Message Title Kevin Huber commented on JENKINS-61388 Re: jiraGetFields: "Illegal base64 character" since 1.5.2 Seems to be related to the changes merged through https://github.com/jenkinsci/jira-steps-plugin/pull/94 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205041.1583744817000.9499.1584627300116%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Mark Waite commented on JENKINS-60630 Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is Alex Z please create a separate ticket since that is a regression between 4.1.1 and 4.2.2. Please also provide the precise description of the job that you are defining, either by uploading the config.xml file from the job definition or by describing the exact steps used to define the job. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.9496.1584627120139%40Atlassian.JIRA.
[JIRA] (JENKINS-61587) don't create remote directory when there are no files to publish
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-61587 don't create remote directory when there are no files to publish Issue Type: Improvement Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2020-03-19 14:09 Priority: Minor Reporter: Jimmy Praet We have a general build pipeline script that is reused by all our projects. It publishes some files to a documentation server with the sshPublisher step. But some projects don't have any documentation, and I would like to have no empty directory created for that project in that case. We see the following: SSH: Connecting from host [dc45dd1bbce5] SSH: Connecting with configuration [doc.cbss.inet] ... SSH: Disconnecting configuration [doc.cbss.inet] ... SSH: Transferred 0 file(s) So no files are transferred, but the configured remoteDirectory is still created, as specified in the documentation: remoteDirectory: Optional destination folder. This folder will be below the one in the global configuration, if present. The folder will be created if does not exist. I tried to specify makeEmptyDirs = false but that has no effect. I don't think that setting applies to the remoteDirectory.
[JIRA] (JENKINS-61587) don't create remote directory when there are no files to publish
Title: Message Title Jimmy Praet created an issue Jenkins / JENKINS-61587 don't create remote directory when there are no files to publish Issue Type: Improvement Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2020-03-19 14:09 Priority: Minor Reporter: Jimmy Praet We have a general build pipeline script that is reused by all our projects. It publishes some files to a documentation server with the sshPublisher step. But some projects don't have any documentation, and I would like to have no empty directory created for that project in that case. We see the following: SSH: Connecting from host [dc45dd1bbce5] SSH: Connecting with configuration [doc.cbss.inet] ... SSH: Disconnecting configuration [doc.cbss.inet] ... SSH: Transferred 0 file(s) So no files are transferred, but the configured remoteDirectory is still created, as specified in the documentation: remoteDirectory: Optional destination folder. This folder will be below the one in the global configuration, if present. The folder will be created if does not exist. I tried to specify makeEmptyDirs = false but that has no effect. I don't think that setting applies to the remoteDirectory.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Lakshmi Prasanna Damineni created an issue Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Issue Type: Bug Assignee: John Westcott Components: ansible-tower-plugin Created: 2020-03-19 13:58 Environment: jenkins version :2.15.0, ansible tower plugin version:0.10.0, Ansible tower version 3.16.1 Priority: Critical Reporter: Lakshmi Prasanna Damineni Ansible Tower Plugin version 0.10.0 does not pass credentials from jenkins job to Ansible tower 3.6.1 version Add Comment
[JIRA] (JENKINS-61518) update notice odd spacing before closing parenthesis
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61518 update notice odd spacing before closing parenthesis Change By: Daniel Beck Labels: newbie-friendly regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205214.158457919.9474.1584624480158%40Atlassian.JIRA.
[JIRA] (JENKINS-61518) update notice odd spacing before closing parenthesis
Title: Message Title Daniel Beck commented on JENKINS-61518 Re: update notice odd spacing before closing parenthesis Steps to reproduce: docker run -p 8080:8080 -p 5:5 jenkins/jenkins:2.225 and get through the setup. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205214.158457919.9471.1584624420146%40Atlassian.JIRA.
[JIRA] (JENKINS-61518) update notice odd spacing before closing parenthesis
Title: Message Title Daniel Beck commented on JENKINS-61518 Re: update notice odd spacing before closing parenthesis This exists exclusively in the popup, and not on Manage Jenkins which isn't really clear from your report (inferred from "Manage Jenkins" link). .page-header__hyperlinks A has a margin-right: 0.25rem; from base-styles-v2.css. Pinging Félix Queiruga Balado – seems like the UI refresh caught more elements than expected due to the popup. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205214.158457919.9469.1584624360135%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title K Z updated JENKINS-61521 Jenkins / JENKINS-61521 "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 Change By: K Z Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9466.1584624180308%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title
Alex Z commented on JENKINS-60630
Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Same problem for me with Git Plugin 4.2.2. I have a pipeline with one branch to be build, it's a paramterized pipeline: refs/tags/${BuildTag}
hudson.plugins.git.GitException: Command "git fetch --tags --progress --prune -- origin +refs/tags/${BuildTag}:refs/remotes/origin/${BuildTag}" returned status code 128:
stdout:
stderr: fatal: Couldn't find remote ref refs/tags/${BuildTag}
fatal: the remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2430)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2044)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:81)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:569)
at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:361)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:197)
at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:173)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:115)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:69)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:427)
Finished: FAILURE
It worked with Git Plugin 4.1.1 and when I restore the plugin to this version it starts to work again! Is this another ticket or should I leave it here? Regards Alex
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Karl Wirth commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Hi Philip Aston Finally got a chance to test this properly and still no luck in reproducing it. Can you please send an email to 'supp...@perforce.com' for my attention and send the full console logs for the two jobs when th. I'll try and figure out what I'm missing. Thanks in advance, Karl Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168534.1456438321000.9440.1584618840223%40Atlassian.JIRA.
[JIRA] (JENKINS-56910) Can no longer search for branch names of parallel() branches
Title: Message Title Simon Harrison commented on JENKINS-56910 Re: Can no longer search for branch names of parallel() branches Please re-instate the parallel branch names in the logs - this backwards step makes debugging & log parsing by other tools much harder. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198583.1554468108000.9435.1584617220136%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-60725 "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Change By: Ramon Leon Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.9430.1584617160789%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61521 "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 Change By: Ramon Leon Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9428.1584617160765%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title Ramon Leon updated JENKINS-61521 Jenkins / JENKINS-61521 "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9425.1584617160729%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title Ramon Leon commented on JENKINS-61521 Re: "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 ethorsa You can see here the exception thrown is ignored: https://github.com/jenkinsci/remoting/blob/33b2847e389c4ee63e21ec0a259c89bec6dfe42d/src/main/java/hudson/remoting/RemoteClassLoader.java#L906 So it's safe to ignore it as well on our telemetry gathering. Thank you for your feedback, it helps us make sure Jenkins is Java11 compatible. PR: https://github.com/jenkinsci/jenkins/pull/4595 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9421.1584617100138%40Atlassian.JIRA.
[JIRA] (JENKINS-55137) No branch name in logs from parallel branches anymore?
Title: Message Title Simon Harrison commented on JENKINS-55137 Re: No branch name in logs from parallel branches anymore? Although this states "Resolved", we still have lost branch names from the logs after updating to version 2.80. This creates problems for us. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196204.1544601655000.9414.1584617040283%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title Ramon Leon started work on JENKINS-61521 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9411.1584616680409%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-61521 "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9409.1584616680380%40Atlassian.JIRA.
[JIRA] (JENKINS-47609) Add an option for a long path
Title: Message Title Rishabh Budhouliya commented on JENKINS-47609 Re: Add an option for a long path PR in git-plugin: https://github.com/jenkinsci/git-plugin/pull/856 In git-client-plugin: https://github.com/jenkinsci/git-client-plugin/pull/523 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186086.150886263.9406.1584613920686%40Atlassian.JIRA.
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-61520 At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Anda Sorina Laakso Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205217.1584601273000.9401.1584611700242%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Oliver Gondža commented on JENKINS-61105 Re: 2.204.3 rc fails to open folder in Java 8, throws class not found exception Proposing fix for core master branch: https://github.com/jenkinsci/jenkins/pull/4594 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204617.1581864893000.9394.1584611580190%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title
ethorsa updated an issue
Jenkins / JENKINS-61521
"Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Change By:
ethorsa
There are a bunch of these cxceptiones in the Jenkins log with a master Master running on AdoptOpenJDK 11 (follow produce warnings related to missing telementry classes. These are found in the jenkins log. Follow up to JENKINS-60725 ) . {noformat}WARNING jenkins.telemetry.impl.java11.MissingClassTelemetry reportExceptionAdded a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactoryjava.lang.ClassNotFoundException: com.sun.jndi.url.java.javaURLContextFactory at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:846) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:889) at jdk.internal.reflect.GeneratedMethodAccessor50.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834){noformat}
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title ethorsa commented on JENKINS-61521 Re: "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 Running a Jenkins Master causes a bunch of exceptions related to missing classes in the Jenkins log. But good point, there should be more information in the first post. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9372.1584607380119%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title Daniel Beck commented on JENKINS-61521 Re: "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 What's the bug being reported here? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9366.1584606000160%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11
Title: Message Title ethorsa updated an issue Jenkins / JENKINS-61521 "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK11 Change By: ethorsa Summary: "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK1 AdoptOpenJDK11 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9364.1584605040069%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Senthilkumar Palanisamy commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Hi, We are facing this issue frequently is there any workaround or any fix. Our Jenkins version 2.204.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.9328.1584603780655%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK1
Title: Message Title ethorsa commented on JENKINS-61521 Re: "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK1 CC Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205218.1584602993000.9326.1584603120051%40Atlassian.JIRA.
[JIRA] (JENKINS-61521) "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK1
Title: Message Title ethorsa created an issue Jenkins / JENKINS-61521 "Added a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory" on AdoptOpenJDK1 Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-19 07:29 Environment: - Jenkins v2.204.5 - AdoptOpenJDK 11.0.4 Labels: adoptopenjdk java11 java11-compatibility Priority: Minor Reporter: ethorsa There are a bunch of these cxceptiones in the Jenkins log with a master running on AdoptOpenJDK 11 (follow up to JENKINS-60725). WARNING jenkins.telemetry.impl.java11.MissingClassTelemetry reportExceptionAdded a missed class for missing class telemetry. Class: com.sun.jndi.url.java.javaURLContextFactory java.lang.ClassNotFoundException: com.sun.jndi.url.java.javaURLContextFactory at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:846) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:889) at jdk.internal.reflect.GeneratedMethodAccessor50.invoke(Unknown Source) at
[JIRA] (JENKINS-60960) Agent-side memory leak (ExportTable retaining some UNIXProcess$ProcessPipeInputStream)
Title: Message Title Kideok Kim commented on JENKINS-60960 Re: Agent-side memory leak (ExportTable retaining some UNIXProcess$ProcessPipeInputStream) I updated durable-task-1.34 and almost slaves are back to normal from the memory leak. Thanks! But there is a few slave still suffered this issue. I appreciate if you let me know any ideas. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204420.1580815533000.9320.1584602040178%40Atlassian.JIRA.
[JIRA] (JENKINS-60960) Agent-side memory leak (ExportTable retaining some UNIXProcess$ProcessPipeInputStream)
Title: Message Title Kideok Kim updated an issue Jenkins / JENKINS-60960 Agent-side memory leak (ExportTable retaining some UNIXProcess$ProcessPipeInputStream) Change By: Kideok Kim Attachment: slave_mem_leak.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204420.1580815533000.9316.1584601980212%40Atlassian.JIRA.
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Govind Sureka created an issue Jenkins / JENKINS-61520 At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2020-03-19 07:01 Environment: Jenkins: CloudBees Jenkins Enterprise 2.176.2.3-rolling hp-application-automation-tools-plugin: 6.1 UFT: 15 Priority: Critical Reporter: Govind Sureka Hello Team, I have setup UFT 15 for Remote execution with Logged Out option. I Sign out of Windows 10 Workstation where UFT15 is installed. There is Jenkins Node on this system. I triggered Freestyle Jenkins job with plugin: Execute Micro Focus functional tests from Micro Focus ALM. It executed the 4 test cases and updated the result in Jenkins console. Then it gave error for JNLP-4 and Job status becomes Failed. Please suggest solution for this on priority. Import section of the logs marked in Red below. Jenkins Console Log: Started by user Sureka Govind (VKS2VDQ) Running as SYSTEM Building remotely on UFT_EntAutomation_N4 (uft-ent-n4) in workspace C:\Program Files\Jenkins\UFT_EntAutomation_N4\workspace\jenkinsmaster-5\ENT\EntAutomation\UFT_Jobs\Test_Under_Progress\GCS_Login_UFT15 No emails were triggered. [GCS_Login_UFT15] $ "C:\Program Files\Jenkins\UFT_EntAutomation_N4\workspace\jenkinsmaster-5\ENT\EntAutomation\UFT_Jobs\Test_Under_Progress\GCS_Login_UFT15\HpToolsLauncher.exe" -paramfile props19032020023521961.txt "Started..." Timeout is set to: -1 Run mode is set to: RUN_REMOTE Unable to retrieve test set folder: Node not found. Starting test set execution Test set name: Regression_GCS_AccountSummary_SearchOpenItems, Test set id: 18802 Test 1:
[JIRA] (JENKINS-59966) Prometheus Plugin: Causes StackOverFlowerError
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59966 Re: Prometheus Plugin: Causes StackOverFlowerError This is supposedly solved in version 2.0.7 of the plugin: https://github.com/jenkinsci/prometheus-plugin/pull/143 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202770.1572283306000.9308.1584600780254%40Atlassian.JIRA.
[JIRA] (JENKINS-47005) Let user specify p4 workspace root in manual config
Title: Message Title Guy Catz commented on JENKINS-47005 Re: Let user specify p4 workspace root in manual config We would also like to see that coming. We need to sync to different drives and therefore must update the root folder. The lack of that prevents us from working smoothly with the p4 plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185384.150594285.9300.1584597900213%40Atlassian.JIRA.
