[JIRA] (JENKINS-54951) Update Project README documentation
Title: Message Title David Olorundare started work on JENKINS-54951 Change By: David Olorundare Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54951) Update Project README documentation
Title: Message Title David Olorundare assigned an issue to David Olorundare Jenkins / JENKINS-54951 Update Project README documentation Change By: David Olorundare Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54743) Contribute JIRA_URL environment variable
Title: Message Title Naresh Rayapati commented on JENKINS-54743 Re: Contribute JIRA_URL environment variable benoit guerin Thank you for the PR I'm on vacation with limited internet, will be back by end of the month will definitely take a look at this. Thanks again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title Bob Lee commented on JENKINS-43758 Re: Parameters disappear from pipeline job after running the job I had the same issue in which my parameters and GitHub Pull Request Builder settings would disappear after a job builds. I had to run my seed job to recreate the project using the Job DSL to get the settings back. What worked for me to fix it was to delete the project then run the seed job. After that my settings stayed. There was probably an invalid config that was left around that caused the bug and deleting the project got rid of it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54965) Create unit tests for code implementations
Title: Message Title David Olorundare updated JENKINS-54965 Jenkins / JENKINS-54965 Create unit tests for code implementations Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat edited a comment on JENKINS-55006 Re: /monitoring/nodes?format=prometheus throws error 500 I can't reproduce the issue in Jenkins 1.251 with monitoring plugin 1.74.There is a root cause exception indeed, but the problem is that Jenkins fails to give you this root cause exception and the stack-trace is of its failure to report the exception. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat commented on JENKINS-55006 Re: /monitoring/nodes?format=prometheus throws error 500 So I have reopened https://issues.jenkins-ci.org/browse/JENKINS-21695 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21695) IllegalStateException: WRITER masks original exception
Title: Message Title evernat reopened an issue In Jenkins 2.138.3 and upgraded Jetty, testing response.isCommitted() does not seem enough to fix this issue. See https://issues.jenkins-ci.org/browse/JENKINS-55006 A catch instead of response.isCommitted() may be needed? Jenkins / JENKINS-21695 IllegalStateException: WRITER masks original exception Change By: evernat Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat commented on JENKINS-55006 Re: /monitoring/nodes?format=prometheus throws error 500 I can't reproduce the issue in Jenkins 1.251 with monitoring plugin 1.74. There is a root cause exception indeed, but the problem is that Jenkins fails to give you this root cause exception and the stack-trace of its failure to report the exception. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10487) Remote API call to get list of enabled plugins for a job
Title: Message Title Ulli Hafner edited a comment on JENKINS-10487 Re: Remote API call to get list of enabled plugins for a job Will be part of warnings Next Generation Plugin 1.0. See [documentation|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#aggregation-summary-of-all-analysis-results]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10487) Remote API call to get list of enabled plugins for a job
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-10487 Remote API call to get list of enabled plugins for a job Change By: Ulli Hafner Comment: I'm not sure if that still makes sense with the planned new features: the results may now use user defined IDs (and urls). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-10487) Remote API call to get list of enabled plugins for a job
Title: Message Title Ulli Hafner resolved as Fixed See documentation. Jenkins / JENKINS-10487 Remote API call to get list of enabled plugins for a job Change By: Ulli Hafner Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55006) /monitoring/nodes?format=prometheus throws error 500
Title: Message Title evernat updated an issue Jenkins / JENKINS-55006 /monitoring/nodes?format=prometheus throws error 500 Change By: evernat Accessing /monitoring/nodes?format=prometheus gives error 500 Error: _java java .lang.IllegalStateException: WRITER_ WRITER _at at org.eclipse.jetty.server.Response.getOutputStream( [ Response.java:917 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.eclipse.jetty.server.Response#917] ) _ _at at javax.servlet.ServletResponseWrapper.getOutputStream( [ ServletResponseWrapper.java:142 |http://ci.corp.atmel.com/mcu/monitoring?part=source=javax.servlet.ServletResponseWrapper#142] ) _ _at at org.kohsuke.stapler.compression.CompressionServletResponse.activate( [ CompressionServletResponse.java:61 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.compression.CompressionServletResponse#61] ) _ _at at org.kohsuke.stapler.compression.CompressionFilter.activate( [ CompressionFilter.java:108 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.compression.CompressionFilter#108] ) _ _at at org.kohsuke.stapler.ResponseImpl.getCompressedOutputStream( [ ResponseImpl.java:302 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.ResponseImpl#302] ) _ _at at org.kohsuke.stapler.jelly.DefaultScriptInvoker.createOutputStream( [ DefaultScriptInvoker.java:88 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.DefaultScriptInvoker#88] ) _ _at at org.kohsuke.stapler.jelly.DefaultScriptInvoker.createXMLOutput( [ DefaultScriptInvoker.java:68 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.DefaultScriptInvoker#68] ) _ _at at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript( [ DefaultScriptInvoker.java:51 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.DefaultScriptInvoker#51] ) _ _at at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch( [ JellyFacet.java:103 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.jelly.JellyFacet$1#103] ) _ _at at org.kohsuke.stapler.Stapler.tryInvoke( [ Stapler.java:739 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.Stapler#739] ) _ _at at org.kohsuke.stapler.Stapler.invoke( [ Stapler.java:870 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.Stapler#870] ) _ _at at org.kohsuke.stapler.Stapler.invoke( [ Stapler.java:668 |http://ci.corp.atmel.com/mcu/monitoring?part=source=org.kohsuke.stapler.Stapler#668] ) _ _at at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0( [ InstallUncaughtExceptionHandler.java:36 |http://ci.corp.atmel.com/mcu/monitoring?part=source=hudson.init.impl.InstallUncaughtExceptionHandler#36] ) _ _at at org.kohsuke.stapler.compression.CompressionFilter.reportException( [ CompressionFilter.java:77
[JIRA] (JENKINS-10487) Remote API call to get list of enabled plugins for a job
Title: Message Title Ulli Hafner reopened an issue Jenkins / JENKINS-10487 Remote API call to get list of enabled plugins for a job Change By: Ulli Hafner Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12194) warnings dashboard view portlet, ability to filter by category or type
Title: Message Title Ulli Hafner resolved as Won't Fix Currently there is no support for portlets anymore. Jenkins / JENKINS-12194 warnings dashboard view portlet, ability to filter by category or type Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17168) Integrate functionality of analysis-collector plug-in into analysis-core
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-17168 Integrate functionality of analysis-collector plug-in into analysis-core Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22526) Health threshold rebaseline command
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-22526 Health threshold rebaseline command Change By: Ulli Hafner Health jjHealth thresholds are based (delta) by comparing against some previous build.When, for an existing job, you add a new checker, or make an existing checker more strict, you typically cause all the health thresholds to be violated.In large, legacy code bases, its never realistic to expect to burn those down by any appreciable amount in any finite time.But, you can however, expect to attempt to contain growth of the newly identified and tracked technical debt.Is it possible to have some sort of UI option, command, whatever to say, "accept this build as the baseline to compare against"The current scenarios to effect this without the option are fairly ugly.Unless I'm missing something, the options as I see them are1. delete the job and recreate it whenever you add or make more strict a checker. This will establish the baseline at build 0 but loose all the trending and historical data2. raise/disable the health threshold gate (e.g from 0 new normal to 10'000 new normal), run a build so you have a new 'stable' base, then drop the limit back down. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-28057) CMake, CPack, CTest parser
Title: Message Title Ulli Hafner resolved as Won't Fix Jenkins / JENKINS-28057 CMake, CPack, CTest parser Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31906) MSBuild warnings raised from CodeAnalyzers(Roslyn) won't be captured
Title: Message Title Ulli Hafner commented on JENKINS-31906 Re: MSBuild warnings raised from CodeAnalyzers(Roslyn) won't be captured Is this still valid? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35012) Compiler warnings per project (portlet) not working
Title: Message Title Ulli Hafner updated JENKINS-35012 The warnings-ng plugin currently does not support portliest anymore. Hopefully I can add such a feature later on. Jenkins / JENKINS-35012 Compiler warnings per project (portlet) not working Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35012) Compiler warnings per project (portlet) not working
Title: Message Title Ulli Hafner updated JENKINS-35012 Jenkins / JENKINS-35012 Compiler warnings per project (portlet) not working Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41822) msbuild warning parser with NullPointerExcetpion
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-41822 msbuild warning parser with NullPointerExcetpion Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45774) Cannot find files from reports generated in parallel
Title: Message Title Ulli Hafner resolved as Fixed As far as I understood the parallel prefix is not shown anymore in the console log. can you confirm? Jenkins / JENKINS-45774 Cannot find files from reports generated in parallel Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48065) GNU Make + GCC C Compiler (gcc) parser catches very few make issues
Title: Message Title Ulli Hafner resolved as Won't Fix I removed the make and gcc parser from the distribution. All functionality should be available in the Gcc4 parsers suite. Does this parser also have the same problems? Jenkins / JENKINS-48065 GNU Make + GCC C Compiler (gcc) parser catches very few make issues Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51902) build-timestamp-plugin does not ignore empty 3rd field 'shift timestamp'
Title: Message Title Jason Davis commented on JENKINS-51902 Re: build-timestamp-plugin does not ignore empty 3rd field 'shift timestamp' Matthew Hall - Thanks for the hack/workaround. I also lost my preconfigured additional timestamps after upgrading the plugin to the latest. Couldn't recreate them until I found this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55211) Build report returns 404 on Jenkins 2.150.1
Title: Message Title Iacopo Pace created an issue Jenkins / JENKINS-55211 Build report returns 404 on Jenkins 2.150.1 Issue Type: Bug Assignee: Unassigned Components: scoverage-plugin Created: 2018-12-14 21:56 Priority: Critical Reporter: Iacopo Pace The project report correctly directs to the latest successful run, while the report for a single job returns a 404. A solution for the 2.150.1 version is in https://github.com/shanbin/scoverage-plugin/pull/25 - haven't checked backwards compatibility (the plugin is reported to be compatible with 1.609.1(. The jenkins fork for the plugin is behind the dev's branch of another commit, fixing a NPE. Add Comment
[JIRA] (JENKINS-55181) Input submitter parameter should use the current IdStrategy to match against current user
Title: Message Title Devin Nusbaum updated JENKINS-55181 Version 2.9 of Pipeline Input Step Plugin was just released with a fix for this issue. Jenkins / JENKINS-55181 Input submitter parameter should use the current IdStrategy to match against current user Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: (towards) pipeline-input-step 2.9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Attachment: samejob.png Attachment: samejob1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Attachment: samejob.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Attachment: samejob1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Summary: Same downstream build is triggered by two different upstream jobs Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream Change By: Kevin Yu [Symptom] There are two upstream jobs, which triggered the same downstream job. When both upstream jobs are triggered at the same time, seems like there's a race condition, which would caused the same build in downstream job triggered only once, by both upstream jobs.[Expected behaviour]Downstream job should be triggered twice, each with different BUILD_NUMBER.Please see screenshoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream Change By: Kevin Yu There are two upstream jobs, which triggered the same downstream job. When both upstream jobs are triggered at the same time, seems like there's a race condition, which would caused the same build in downstream job triggered only once, by both upstream jobs. [ Expected behaviour ]Downstream job should be the downstream job is triggered twice , each with different BUILD_NUMBER .Please see screenshoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream
Title: Message Title Kevin Yu created an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream Issue Type: Bug Assignee: Unassigned Attachments: samejob.png, samejob1.png Components: core Created: 2018-12-14 21:09 Environment: Jenkins ver. 2.46.2 Priority: Major Reporter: Kevin Yu There are two upstream jobs, which triggered the same downstream job. When both upstream jobs are triggered at the same time, seems like there's a race condition, which would caused the same build in downstream job triggered only once, by both upstream jobs. Expected behaviour should be the downstream job is triggered twice. Please see screenshoot Add Comment
[JIRA] (JENKINS-52943) Blue Ocean view does not show descriptions for shell steps with multiple arguments
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-52943 Blue Ocean view does not show descriptions for shell steps with multiple arguments Change By: Devin Nusbaum Summary: Blue Ocean view does not show descriptions for shell steps with `returnStdout: true` multiple arguments Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52943) Blue Ocean view does not show descriptions for shell steps with multiple arguments
Title: Message Title Devin Nusbaum updated JENKINS-52943 A fix for this issue was just released in version 2.27 of Pipeline Nodes and Processes Plugin. Jenkins / JENKINS-52943 Blue Ocean view does not show descriptions for shell steps with multiple arguments Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-durable-task-step 2.27 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55209) p4 groovy commands with 300 second timeout
Title: Message Title
Sean Sutherland updated an issue
Jenkins / JENKINS-55209
p4 groovy commands with 300 second timeout
Change By:
Sean Sutherland
We're seeing an issue where an unshelve command through a p4groovy object is timing out after 5 minutes. There's no other information besides an InterruptedException {quote} *00:31:58* [windows-pipeline || windows-pipeline-main-8-0] Unshelve shelve sync label: 292428[Pipeline] [windows-pipeline || windows-pipeline-main-8-0] p4[Pipeline] [Scheduler] }[Pipeline] [windows-pipeline || windows-pipeline-main-8-0] }[Pipeline] [Scheduler] {[Pipeline] [windows-pipeline || windows-pipeline-main-8-0] // ws[Pipeline] [windows-pipeline || windows-pipeline-main-8-0] echo*00:36:58* [windows-pipeline || windows-pipeline-main-8-0] Exception running batch java.lang.InterruptedException {quote} Code snippet{quote}def p4client = jenkins.p4(credential: context.p4credentials, workspace: workspace)def result = p4client.run('unshelve', '-f', '-s', context.shelveSyncLabel.toString()) {quote} Call stack snippet {quote} [Pipeline] End of Pipelinejava.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.Channel.call(Channel.java:954) at hudson.FilePath.act(FilePath.java:1036) at hudson.FilePath.act(FilePath.java:1025) at org.jenkinsci.plugins.p4.groovy.P4Groovy.run(P4Groovy.java:63) at sun.reflect.GeneratedMethodAccessor975.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) {quote} This looks to be the same issue as JENKINS-44427 but I'm not sure how to apply that fix to p4 groovy as well.
Add Comment
[JIRA] (JENKINS-55209) p4 groovy commands with 300 second timeout
Title: Message Title
Sean Sutherland created an issue
Jenkins / JENKINS-55209
p4 groovy commands with 300 second timeout
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-12-14 20:49
Labels:
p4-plugin
Priority:
Major
Reporter:
Sean Sutherland
We're seeing an issue where an unshelve command through a p4groovy object is timing out after 5 minutes. There's no other information besides an InterruptedException 00:31:58 [windows-pipeline || windows-pipeline-main-8-0] Unshelve shelve sync label: 292428 [Pipeline] [windows-pipeline || windows-pipeline-main-8-0] p4 [Pipeline] [Scheduler] } [Pipeline] [windows-pipeline || windows-pipeline-main-8-0] } [Pipeline] [Scheduler] { [Pipeline] [windows-pipeline || windows-pipeline-main-8-0] // ws [Pipeline] [windows-pipeline || windows-pipeline-main-8-0] echo*00:36:58* [windows-pipeline || windows-pipeline-main-8-0] Exception running batch java.lang.InterruptedException Code snippet
def p4client = jenkins.p4(credential: context.p4credentials, workspace: workspace)
def result = p4client.run('unshelve', '-f', '-s', context.shelveSyncLabel.toString())
Call stack snippet [Pipeline] End of Pipeline java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.Channel.call(Channel.java:954) at hudson.FilePath.act(FilePath.java:1036) at hudson.FilePath.act(FilePath.java:1025) at org.jenkinsci.plugins.p4.groovy.P4Groovy.run(P4Groovy.java:63) at sun.reflect.GeneratedMethodAccessor975.invoke(Unknown Source)
[JIRA] (JENKINS-55208) Jenkins pipeline multi line sh script behave different in access global variable
Title: Message Title
Simon Le updated an issue
Jenkins / JENKINS-55208
Jenkins pipeline multi line sh script behave different in access global variable
Change By:
Simon Le
A global variable can be print in single line shell but not in multi line script. With the script: {noformat} def my_var = "my_value"pipeline {agent anystages {stage('Build') {steps {sh "echo my_var=${my_var}"sh '''echo my_var=${my_var}'''}}}} {noformat} I got the result: {noformat} [Pipeline] sh+ echo my_var=my_valuemy_var=my_value[Pipeline] sh+ echo my_var=my_var=[Pipeline] } {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Anatoly Shirokov updated an issue Jenkins / JENKINS-55106 Build stuck on final "exit 0" Change By: Anatoly Shirokov Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Devin Nusbaum commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs I don't think the changes in workflow-job 2.29 and workflow-api 2.32 related to WorkflowRun#getLogFile are related to an empty console view, since the WorkflowRun#getLogFile method is not actually used when displaying logs. The stack trace you posted shows that the call to new RandomAccessFile here threw a FileNotFoundException when trying to open the logs for a step because the log file did not exist. What does the build folder for the build look like? Does the log file exist? Are there any other errors in the Jenkins logs that seem relevant? It seems like something else might have deleted that file, but I am not sure what could have caused it. Do you know if the build that was broken was building when Jenkins was restarted for the plugin update, or had it already completed? CC Jesse Glick in case this scenario rings a bell to him. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55208) Jenkins pipeline multi line sh script behave different in access global variable
Title: Message Title
Simon Le created an issue
Jenkins / JENKINS-55208
Jenkins pipeline multi line sh script behave different in access global variable
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-12-14 19:48
Environment:
Jenkins ver. 2.107.3
Priority:
Minor
Reporter:
Simon Le
A global variable can be print in single line shell but not in multi line script. With the script: def my_var = "my_value" pipeline { agent any stages { stage('Build') { steps { sh "echo my_var=${my_var}" sh ''' echo my_var=${my_var} ''' } } } } I got the result: [Pipeline] sh + echo my_var=my_value my_var=my_value [Pipeline] sh + echo my_var= my_var= [Pipeline] }
Add Comment
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title
Anatoly Shirokov edited a comment on JENKINS-55106
Re: Build stuck on final "exit 0"
Confirmed. The same issue with 2.150.1 on Windows 2003, JDK 8 . As you see exactly 10 minutes before the finish: {code:java} 19:59:42 D:\Jenkins\jobs\product\workspace>echo done 19:59:42 done 19:59:42 19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 20:09:44 Finished: SUCCESS{code}We have reverted to the 2.138.2 version.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title
Anatoly Shirokov edited a comment on JENKINS-55106
Re: Build stuck on final "exit 0"
Confirmed. The same issue with 2.150.1 on Windows Server 2003, JDK 8. As you see exactly 10 minutes before the finish: {code:java} 19:59:42 D:\Jenkins\jobs\product\workspace>echo done 19:59:42 done 19:59:42 19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 20:09:44 Finished: SUCCESS{code}We have reverted to the 2.138.2 version.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54833) Warnings Parser fails parsing log
Title: Message Title Ulli Hafner updated JENKINS-54833 Jenkins / JENKINS-54833 Warnings Parser fails parsing log Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title
Anatoly Shirokov edited a comment on JENKINS-55106
Re: Build stuck on final "exit 0"
Confirmed. The same issue with 2.150.1. As you see exactly 10 minutes before finished: ``` {code:java} 19:59:42 D:\Jenkins\jobs\product\workspace>echo done 19:59:42 done19:59:42 19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 20:09:44 Finished: SUCCESS {code} ``` We have reverted to the 2.138.2 version.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title
Anatoly Shirokov edited a comment on JENKINS-55106
Re: Build stuck on final "exit 0"
Confirmed. The same issue with 2.150.1. As you see exactly 10 minutes before finished the finish : {code:java} 19:59:42 D:\Jenkins\jobs\product\workspace>echo done 19:59:42 done 19:59:42 19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 20:09:44 Finished: SUCCESS{code}We have reverted to the 2.138.2 version.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Anatoly Shirokov edited a comment on JENKINS-55106 Re: Build stuck on final "exit 0" Confirmed. The same issue with 2.150.1. As you see exactly 10 minutes before finished : ```19:59:42 D:\Jenkins\jobs\product\workspace>echo done 19:59:42 done19:59:42 19:59:42 D:\Jenkins\jobs\product\workspace>exit 0 20:09:44 Finished: SUCCESS```We have reverted to the 2.138.2 version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55207) NPE at au.com.rayh.BuildConfiguration.(BuildConfiguration.java:47)
Title: Message Title
Alexey Molchanov created an issue
Jenkins / JENKINS-55207
NPE at au.com.rayh.BuildConfiguration.(BuildConfiguration.java:47)
Issue Type:
Bug
Assignee:
Unassigned
Components:
xcode-plugin
Created:
2018-12-14 19:14
Priority:
Blocker
Reporter:
Alexey Molchanov
NPE at au.com.rayh.BuildConfiguration.(BuildConfiguration.java:47) this.provisioningProfileUUID = buildSettingsDict.objectForKey("PROVISIONING_PROFILE").toString(); "PROVISIONING_PROFILE" is now deprecated, value needs to be checked for null.
Add Comment
[JIRA] (JENKINS-24463) PyLint parse missing errors
Title: Message Title Ulli Hafner updated JENKINS-24463 Jenkins / JENKINS-24463 PyLint parse missing errors Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46779) Suppress blaming for shallow git clones
Title: Message Title Ulli Hafner updated JENKINS-46779 Jenkins / JENKINS-46779 Suppress blaming for shallow git clones Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54402) Pipeline Syntax page is missing the dropdown for supported parsers
Title: Message Title Ulli Hafner updated JENKINS-54402 Jenkins / JENKINS-54402 Pipeline Syntax page is missing the dropdown for supported parsers Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49911) Release 2.0 of the static analysis suite
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-49911 Release 2.0 of the static analysis suite Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Anatoly Shirokov commented on JENKINS-55106 Re: Build stuck on final "exit 0" The same issue: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42755) BFA fails to catch pipeline related exceptions
Title: Message Title Will Freeman commented on JENKINS-42755 Re: BFA fails to catch pipeline related exceptions The timestamps thing I expect, however, we experience the exact same issue as the OP. It appears anything output from stderr is not processed by BFA on the build run, but only after in the subsequent scan. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54982) Using Java8 Streams evaluates whole expression to Boolean
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-54982 Using Java8 Streams evaluates whole _expression_ to Boolean Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54982) Using Java8 Streams evaluates whole expression to Boolean
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-54982 Using Java8 Streams evaluates whole _expression_ to Boolean Change By: Devin Nusbaum Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54982) Using Java8 Streams evaluates whole expression to Boolean
Title: Message Title Devin Nusbaum commented on JENKINS-54982 Re: Using Java8 Streams evaluates whole _expression_ to Boolean I reproduced this with some quick testing. I think this is very similar to JENKINS-26481, for which I am not familiar with the full fix, but I think it involved rewriting DefaultGroovyMethods directly in groovy-cps, which I guess we can't really do here as this involves Java Platform code rather than groovy code, but I'm not completely sure. CC Andrew Bayer who worked on the fix for JENKINS-26481 and might have a better idea. You might be able to replace this with something equivalent that uses Groovy language features instead of the Stream API as a workaround. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55159) Installing MicroFocus HP Automation tools plugin breaks Jenkins v2.150.1
Title: Message Title Benjamin Watson commented on JENKINS-55159 Re: Installing MicroFocus HP Automation tools plugin breaks Jenkins v2.150.1 I installed the Maven Integration Plugin, safely restarted Jenkins, then installed the HP/MicroFocus plugin, restarted Jenkins, and all seems well. Thanks for the tip Artem Shorokhov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-53346 GitSCM checkout returns same values on second different call Change By: Mark Waite Hi,if I run within a pipeline job, the checkout command twice to checkout different commits, the returnvalue of this call has two times the same values, even if the branches and commits are different.E.g:def scm1 = checkout (changelog: false, poll: false, verboseEnabled: false, scm: [$class: 'GitSCM', branches: [[name: 'refs/tags/TAG1']], )def scm2 = checkout (changelog: false, poll: false, verboseEnabled: false, scm: [$class: 'GitSCM', branches: [[name: 'refs/tags/TAG2']], ...)the Maps scm1 and scm2 contain the same values, even if the tags are on different commits.And the values are always from the first checkout :(.So how can I get such values from the second checkout? Note that this problem is specific to performing multiple checkouts from the *same repository* with different SHA1 hashes in the same Pipeline job. If different repositories are used in the same Pipeline job, refer to JENKINS-39968. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-54929) Some final output is missing in Jenkins Pipeline when using the Ansible Plugin
Title: Message Title Ben Specht updated an issue Jenkins / JENKINS-54929 Some final output is missing in Jenkins Pipeline when using the Ansible Plugin Change By: Ben Specht Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55153) Depends on EasySSLProtocolSocketFactory from git-client 2.0
Title: Message Title Mark Waite commented on JENKINS-55153 Re: Depends on EasySSLProtocolSocketFactory from git-client 2.0 The class is also available in jenkinsci/lib-commons-httpclient if that helps. I don't plan to restore this to the git client plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43470) mvn perform:release fails because settings using -D are ignored
Title: Message Title Cyrille Le Clerc closed an issue as Cannot Reproduce Close as cannot reproduce. Please reopen an issue if the problem is still there. Jenkins / JENKINS-43470 mvn perform:release fails because settings using -D are ignored Change By: Cyrille Le Clerc Status: In Progress Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21426) ENOENT during archiving artifacts
Title: Message Title Cyrille Le Clerc commented on JENKINS-21426 Re: ENOENT during archiving artifacts Kenneth Baltrinic do you reproduce this bug? I didn't see this problem happening anywhere Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41889) Environment variables available in the Jenkinsfile are not propagated to Maven
Title: Message Title Cyrille Le Clerc closed an issue as Cannot Reproduce Close as cannot reproduce. Please open a new ticket with more detaisl if the problem is still here. Jenkins / JENKINS-41889 Environment variables available in the Jenkinsfile are not propagated to Maven Change By: Cyrille Le Clerc Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Jesse Glick commented on JENKINS-54834 Re: Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml Option 1 is probably easier from my PoV as well. Either way, the main issue I see is that the input must explicitly mention all transitive dependencies, so that they are all listed as eligible for upgrade by the bot. (Perhaps using dependencyManagement to clearly separate those plugins which are required on their own merits vs. those which are just there to satisfy the transitive closure.) I have had a similar issue with Evergreen and am not sure if it is resolved yet. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52943) Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Title: Message Title Devin Nusbaum assigned an issue to Gavin Mogan Jenkins / JENKINS-52943 Blue Ocean view does not show descriptions for shell steps with `returnStdout: true` Change By: Devin Nusbaum Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52943) Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Title: Message Title Devin Nusbaum updated JENKINS-52943 Jenkins / JENKINS-52943 Blue Ocean view does not show descriptions for shell steps with `returnStdout: true` Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52943) Blue Ocean view does not show descriptions for shell steps with `returnStdout: true`
Title: Message Title Devin Nusbaum started work on JENKINS-52943 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55016) Fix UtilTest.testDeleteRecursive_onWindows flaky test
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-55016 Fix UtilTest.testDeleteRecursive_onWindows flaky test Change By: Matt Sicker Assignee: Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55016) Fix UtilTest.testDeleteRecursive_onWindows flaky test
Title: Message Title Matt Sicker started work on JENKINS-55016 Change By: Matt Sicker Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14064) Use make output to map relative paths to absolute paths
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-14064 Use make output to map relative paths to absolute paths Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: beta8 (warnings-ng), beta17 (analysis-model-api) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) Gcc parser does not resolve absolute paths
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-54035 Gcc parser does not resolve absolute paths Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: beta8 (warnings-ng), beta17 (analysis-model-api) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54750) Multiple charts of same type not shown on job summary page
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-54750 Multiple charts of same type not shown on job summary page Change By: Ulli Hafner Released As: beta8 (warnings-ng), beta17 (analysis-model-api) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54703) Body font-size gets overridden on analysis report page
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-54703 Body font-size gets overridden on analysis report page Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: beta8 (warnings-ng), beta17 (analysis-model-api) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev commented on JENKINS-54834 Re: Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml https://github.com/oleg-nenashev/ci.jenkins.io-runner prototypes the option 1. Once JENKINS-54391 is ready, it can be used for real-world updates CD for Jenkinsfile Runner. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54858) Detect working directory from build output
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-54858 Detect working directory from build output Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: beta8 (warnings-ng), beta17 (analysis-model-api) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54750) Multiple charts of same type not shown on job summary page
Title: Message Title Ulli Hafner resolved as Fixed beta8 (warnings-ng), beta17 (analysis-model-api) Jenkins / JENKINS-54750 Multiple charts of same type not shown on job summary page Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev updated JENKINS-54834 Jenkins / JENKINS-54834 Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54834 Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54834) Create a Dependabot equivalent for CWP plugin lists or add support of Jenkins updates to pom.xml
Title: Message Title Oleg Nenashev started work on JENKINS-54834 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55206) Multiple jenkinsfiles to configure different environments
Title: Message Title chakravarthy garimella created an issue Jenkins / JENKINS-55206 Multiple jenkinsfiles to configure different environments Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-12-14 17:09 Priority: Minor Reporter: chakravarthy garimella I am trying to use multiple jenkinsfiles for different environments. Let say i have DEV, TEST, PROD. i do not want to automate all three environments in single jenkinsfile. I want to manually trigger Test and Prod environments. Is that functionality available in current Jenkins implementation? Add Comment
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Neil Calverley edited a comment on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Another one here, experiencing same issue as Paulius Bulotas and seems to be related to a recent Jenkins update.I have 2 Jenkins instances, one running v2.138.1 with Ansible Plugin v1.0 which is working fine.The other running Jenkins v2.1.50.1 and Ansible Plugin v1.0 which shows the same issue as above. Both tested running the same version of ansible v2.7.2 on same Linux host. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Neil Calverley commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Another one here, experiencing same issue as Paulius Bulotas and seems to be related to a recent Jenkins update. I have 2 Jenkins instances, one running v2.138.1 with Ansible Plugin v1.0 which is working fine. The other running Jenkins v2.1.50.1 and Ansible Plugin v1.0 which shows the same issue as above. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Stefan Verhoeff commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive Same issue again after accidentally upgrading to ec2-1.41 and Jenkins LTS 2.150.1. Looks like this bug is a duplicate, linking: JENKINS-53858 Fix for JENKINS-53858 has been announced for 1.42 on the wiki: https://wiki.jenkins.io/display/JENKINS/Amazon+EC2+Plugin#AmazonEC2Plugin-Version1.42(NotReleaseyet,2018) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title
Thomas Heidrich edited a comment on JENKINS-43210
Re: Windows Agent can't connect to Master through JNLP
In reference to my [code comment|https://github.com/jenkinsci/jenkins/commit/71cbe0cc7c601c04509faa618b23194335288fee#r31678933], why is the certificate of the JNLP4-Protocol being generated during runtime and not changable by configuration? How is the agent supposed to validate the certificate? Am I missing something? My agents always report the following during JNLP4 connection attempts: {noformat}Caused by: java.security.cert.CertificateException: Public key of the first certificate in chain (subject: C=US, OU=jenkins.io, O=instances, CN=deadbeefdeadbeefdeadbeef) is not in the list of trusted keys{noformat} JNLP3 works fine though, but I want the newer secure stuff.Is the public key supposed to be transferred in the encrypted and authenticated transfer of slave-agent.jnlp?UPDATED: Interesting, debugging the agent revealed that the publicKey seems to be transferred, but in my case, this doesn't seem to work.{noformat}INFORMATION: Agent discovery successful Agent address: jenkins.mycorp Agent port:5 Identity: null{noformat} RESOLVED: (/) My reverse proxy dropped the header _X-Instance-Identity_ which is being used in the [remoting lib|https://github.com/jenkinsci/remoting/blob/master/src/main/java/org/jenkinsci/remoting/engine/JnlpAgentEndpointResolver.java#L248-L269] to transfer the public key to the agents. The following Apache directive is a bad idea in case one wants to use agents.{noformat}Header unset X-Instance-Identity{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55204) Maven plugin (version 3.1) is not using the libembedder corresponding to the used maven version
Title: Message Title Javier Raez created an issue Jenkins / JENKINS-55204 Maven plugin (version 3.1) is not using the libembedder corresponding to the used maven version Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-12-14 16:11 Environment: Maven plugin 3.1 Maven version 3.3.3 Jenkins version 2.73.32.0.1 Priority: Minor Reporter: Javier Raez It seems the maven plugin (version 3.1) is not using the libembedder corresponding to the used maven version. This makes that when using a maven feature available in the used maven version (wildcard exclusions, in maven 3.3.3), we observe an error. 10:19:59 [WARNING] 'dependencyManagement.dependencies.dependency.exclusions.exclusion.artifactId' for com.x:xxx:jar with value '*' does not match a valid id pattern. @ xx:5.0.0-SNAPSHOT, C:\Jenkins\workspace\x\develop\x\.repository\com\\xx\enterprise.dependencies\5.0.0-SNAPSHOT\enterprise.dependencies-5.0.0-SNAPSHOT.pom, line 675, column 37 10:19:59 10:19:59 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364) 10:19:59 at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) 10:19:59 at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) 10:19:59 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1328)
[JIRA] (JENKINS-55205) Review findbugs error with some OS+JDK
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-55205 Review findbugs error with some OS+JDK Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2018-12-14 16:12 Environment: linux JDK11 windows JDK8 windows JDK11 Priority: Minor Reporter: Ivan Fernandez Calvo After this PR findbugs claim for some attention [INFO] org.jenkinsci.plugins.saml.BundleKeyStore.saveKeyStore(File, KeyStore, String) may fail to clean up java.io.OutputStream [org.jenkinsci.plugins.saml.BundleKeyStore, org.jenkinsci.plugins.saml.BundleKeyStore, org.jenkinsci.plugins.saml.BundleKeyStore, org.jenkinsci.plugins.saml.BundleKeyStore, org.jenkinsci.plugins.saml.BundleKeyStore] Obligation to clean up resource created at BundleKeyStore.java:[line 184] is not dischargedPath continues at BundleKeyStore.java:[line 186]Path continues at BundleKeyStore.java:[line 188]Path continues at BundleKeyStore.java:[line 189]Path continues at BundleKeyStore.java:[line 190] OBL_UNSATISFIED_OBLIGATION [INFO] The field org.jenkinsci.plugins.saml.SamlAuthenticationToken.session is transient but isn't set by deserialization [org.jenkinsci.plugins.saml.SamlAuthenticationToken] In SamlAuthenticationToken.java SE_TRANSIENT_FIELD_NOT_RESTORED [INFO] Nullcheck of in at line 30 of value previously dereferenced in org.jenkinsci.plugins.saml.SamlValidateIdPMetadata.process() [org.jenkinsci.plugins.saml.SamlValidateIdPMetadata, org.jenkinsci.plugins.saml.SamlValidateIdPMetadata] At SamlValidateIdPMetadata.java:[line 30]Redundant null check at SamlValidateIdPMetadata.java:[line 38]
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title
Thomas Heidrich edited a comment on JENKINS-43210
Re: Windows Agent can't connect to Master through JNLP
In reference to my [code comment|https://github.com/jenkinsci/jenkins/commit/71cbe0cc7c601c04509faa618b23194335288fee#r31678933], why is the certificate of the JNLP4-Protocol being generated during runtime and not changable by configuration? How is the agent supposed to validate the certificate? Am I missing something? My agents always report the following during JNLP4 connection attempts:{noformat}Caused by: java.security.cert.CertificateException: Public key of the first certificate in chain (subject: C=US, OU=jenkins.io, O=instances, CN=deadbeefdeadbeefdeadbeef) is not in the list of trusted keys{noformat}JNLP3 works fine though, but I want the newer secure stuff.Is the public key supposed to be transferred in the encrypted and authenticated transfer of slave-agent.jnlp? UPDATED: Interesting, debugging the agent revealed that the publicKey seems to be transferred, but in my case, this doesn't seem to work.{noformat}INFORMATION: Agent discovery successful Agent address: jenkins.mycorp Agent port:5 Identity: null{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52958) Slave pod is not removed when a job is finished
Title: Message Title Jonas Büttner commented on JENKINS-52958 Re: Slave pod is not removed when a job is finished Also with Jenkins ver. 2.150.1 and Kubernetes plugin 1.13.7 Configuration: Pod Retention = Always Time in minutes to retain agent when idle = 5 Result: Pod Status after Agent remove = Terminated: Completed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55090) Make MySQL the recommended database
Title: Message Title Cyrille Le Clerc updated JENKINS-55090 Jenkins / JENKINS-55090 Make MySQL the recommended database Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55010) Failure to collect pom.xml file path when using flatten-maven-plugin with a non default "flattenedPomFilename"
Title: Message Title Cyrille Le Clerc updated JENKINS-55010 Jenkins / JENKINS-55010 Failure to collect pom.xml file path when using flatten-maven-plugin with a non default "flattenedPomFilename" Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Joe Rioux commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" We are experiencing the same, and also have to reboot our server several times per day. Then sometimes it goes for days without a problem. I filed this bug - https://issues.jenkins-ci.org/browse/JENKINS-54894 We are going to try creating a new server to resolve this since we also have 2 other servers, configured nearly the same as the one we keep having to reboot. The new one will be identical to the 2 we don't have a problem on. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Thomas Heidrich commented on JENKINS-43210 Re: Windows Agent can't connect to Master through JNLP In reference to my code comment, why is the certificate of the JNLP4-Protocol being generated during runtime and not changable by configuration? How is the agent supposed to validate the certificate? Am I missing something? My agents always report the following during JNLP4 connection attempts: Caused by: java.security.cert.CertificateException: Public key of the first certificate in chain (subject: C=US, OU=jenkins.io, O=instances, CN=deadbeefdeadbeefdeadbeef) is not in the list of trusted keys JNLP3 works fine though, but I want the newer secure stuff. Is the public key supposed to be transferred in the encrypted and authenticated transfer of slave-agent.jnlp? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46894) Provide means of detecting cause of build from declarative pipeline
Title: Message Title
Jose Blas Camacho Taboada commented on JENKINS-46894
Re: Provide means of detecting cause of build from declarative pipeline
Costin Caraivan, you can check the documentation here: https://jenkins.io/doc/book/pipeline/syntax/#declarative-pipeline And an example is: when { triggeredBy 'SCMTrigger' } or TimerTrigger
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54667) Getting Error while accessing Performance Report
Title: Message Title Artem Fedorov commented on JENKINS-54667 Re: Getting Error while accessing Performance Report Sure I've just released the new version with this fix. It'll be available soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46239) Address user confusion with veracode-scanner plugin
Title: Message Title Mike Bockus commented on JENKINS-46239 Re: Address user confusion with veracode-scanner plugin Tim Jarrett I think we spoke a few months back about unpublishing this plugin when the official veracode plugin is published. I don't think this open source plugin is necessary anymore since Veracode has an official supported plugin. If you would like, we could look into transitioning ownership of this plugin so the official Veracode plugin could be published and the users could just update to the supported version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Raphael Pionke assigned an issue to Unassigned Jenkins / JENKINS-55202 Performance Signature Plugin: JAXB API is missing with Java 11 Change By: Raphael Pionke Assignee: Raphael Pionke Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34313) Exceptions by parallel SCM checkout
Title: Message Title Shannon Kerr commented on JENKINS-34313 Re: Exceptions by parallel SCM checkout Aaron Dietz well, I've had two occurrences of the issue since the new lock implementation. Just to be clear about what we're doing, we are running at least 3 svn co's in parallel via a call to our groovy script. These checkouts are happening on 3 different machines (one Linux physical machine for docker builds and 2 Windows VMs), all 3 checkouts in parallel. I assume when others are doing checkouts that they too are running parallel checkouts on different machines, but thought I'd better clarify. Are there any other changes you (or others) recommend we try to stop these issues? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
