[JIRA] (JENKINS-50558) Valgrind plugin results error
Title: Message Title Xuezhong Yan commented on JENKINS-50558 Re: Valgrind plugin results error I just manually applied the GitHub PR: https://github.com/jenkinsci/valgrind-plugin/pull/16 and built the plugin myself(0.29-SNAPSHOT). And then "Oops" page disappeared. Hopefully the author will approve the PR soon. FYI. Apply a PR. git fetch origin pull/16/head:jenkins_50558 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-55613) OWASP Dependency Check Plugin hangs forever
Title: Message Title Fly Cricket created an issue Jenkins / JENKINS-55613 OWASP Dependency Check Plugin hangs forever Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-01-16 07:51 Priority: Major Reporter: Fly Cricket Sometimes it happens that the OWASP Dependency Check Plugin starts and hangs forever. When this situation occurs the whole Jenkins Server is blocked. The hanging Job cannot be canceled via the Jenking UI. The Jenkins JVM has to be restarted. Building on master in workspace /.mntpts/sdb1/jenkins/jobs/NVD-UPDATE/workspace [DependencyCheck] OWASP Dependency-Check Plugin v4.0.2 [DependencyCheck] Executing Dependency-Check with the following options: [DependencyCheck] -name = NVD-UPDATE [DependencyCheck] -outputDirectory = /.mntpts/sdb1/jenkins/jobs/NVD-UPDATE/workspace [DependencyCheck] -dataDirectory = /.mntpts/sdb1/nvd [DependencyCheck] -dataMirroringType = none [DependencyCheck] -isQuickQueryTimestampEnabled = true [DependencyCheck] -jarAnalyzerEnabled = false [DependencyCheck] -nodePackageAnalyzerEnabled = false [DependencyCheck] -nodeAuditAnalyzerEnabled = false [DependencyCheck] -retireJsAnalyzerEnabled = true [DependencyCheck] -composerLockAnalyzerEnabled = false [DependencyCheck] -pythonDistributionAnalyzerEnabled = false [DependencyCheck] -pythonPackageAnalyzerEnabled = false [DependencyCheck] -rubyBundlerAuditAnalyzerEnabled = false [DependencyCheck] -rubyGemAnalyzerEnabled = false [DependencyCheck] -cocoaPodsAnalyzerEnabled = false [DependencyCheck] -swiftPackageManagerAnalyzerEnabled = false [DependencyCheck] -archiveAnalyzerEnabled = false [DependencyCheck] -assemblyAnalyzerEnabled = false [DependencyCheck] -msBuildProjectAnalyzerEnabled = false [DependencyCheck] -nuGetConfigAnalyzerEnabled = false [DependencyCheck] -nuspecAnalyzerEnabled = false [DependencyCheck] -centralAnalyzerEnabled = false [DependencyCheck] -nexusAnalyzerEnabled = false [DependencyCheck] -artifactoryAnalyzerEnabled = false
[JIRA] (JENKINS-55446) Unable to Execute Test in HP Performance Center 12.01
Title: Message Title Pradeepkumar Subramaniam stopped work on JENKINS-55446 Change By: Pradeepkumar Subramaniam Status: In Progress Open 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-52769) Environment variables defined in pipeline not expanding in docker args
Title: Message Title William Laszlo updated an issue Jenkins / JENKINS-52769 Environment variables defined in pipeline not expanding in docker args Change By: William Laszlo Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55612) Add optional label attribute for echo step to improve usability
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-55612 Add optional label attribute for echo step to improve usability Issue Type: Improvement Assignee: Unassigned Attachments: image-2019-01-16-07-21-46-096.png, image-2019-01-16-07-22-30-193.png Components: pipeline Created: 2019-01-16 06:24 Environment: The greatest and latest official releases Priority: Minor Reporter: Reinhold Füreder Similar to JENKINS-55410 Why? Seemingly if the message for echo step is too long, it solely prints "Print Message" in pipeline view, while for short messages it prints the message nicely: vs. For the latter I would like to set an optional label to e.g. "PhpStorm inspection results". Add Comment
[JIRA] (JENKINS-55611) Make EXECUTOR_NUMBER available for yaml definition
Title: Message Title Drum Big created an issue Jenkins / JENKINS-55611 Make EXECUTOR_NUMBER available for yaml definition Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-01-16 04:16 Priority: Minor Reporter: Drum Big We have a use case that we would like to attach persistent volume to the pod during the build (to store cache data). To support concurrent build, we would like to assign volume claim based on the EXECUTOR_NUMBER, so that different concurrent build can use different volume. Currently, this is impossible since EXECUTOR_NUMBER is not available in the agent definition. Add Comment
[JIRA] (JENKINS-55610) CloudShell Sandbox Plugin not compatible with JEP-200
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-55610 Re: CloudShell Sandbox Plugin not compatible with JEP-200 The more straightforward solution is to add src/main/resources/META-INF/hudson.remoting.ClassFilter with the content: com.quali.cloudshell.QsServerDetails Another solution could be to store the details (serverAddress, user, pw, domain, ignoreSSL) and declare QsServerDetails server as transient 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-55610) CloudShell Sandbox Plugin not compatible with JEP-200
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-55610 CloudShell Sandbox Plugin not compatible with JEP-200 Change By: Allan BURDAJEWICZ Labels: JEP-200 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-55610) CloudShell Sandbox Plugin not compatible with JEP-200
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-55610 CloudShell Sandbox Plugin not compatible with JEP-200 Issue Type: Bug Assignee: Tomer Admon Components: cloudshell-sandbox-plugin Created: 2019-01-16 03:54 Environment: Jenkins 2.138.4 cloudshell-sandbox: 1.6.3 Priority: Critical Reporter: Allan BURDAJEWICZ The Global Configuration fails to persists. In the Jenkins logs, we see the following stacktrace: 2019-01-14 18:37:40.491+ [id=1812009] WARNING hudson.model.Descriptor#save: Failed to save /var/lib/jenkins/org.jenkinsci.plugins.cloudshell.CloudShellConfig.xml java.lang.UnsupportedOperationException: Refusing to marshal com.quali.cloudshell.QsServerDetails for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.cloudshell.CloudShellConfig$DescriptorImpl#server for class org.jenkinsci.plugins.cloudshell.CloudShellConfig$DescriptorImpl at
[JIRA] (JENKINS-55609) Submitted JCL no longer supports variable substitution
Title: Message Title Daniel Stratton updated an issue Jenkins / JENKINS-55609 Submitted JCL no longer supports variable substitution Change By: Daniel Stratton Environment: Jenkins 2.150.1 on Windows 10 1809 64-bitIBM z/OS Connector 2.0.1EnvInject API Plugin 1.5Environment Injector Plugin 2.1.6 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-55609) Submitted JCL no longer supports variable substitution
Title: Message Title Daniel Stratton created an issue Jenkins / JENKINS-55609 Submitted JCL no longer supports variable substitution Issue Type: Bug Assignee: Alexander Shcherbakov Components: zos-connector-plugin Created: 2019-01-16 02:38 Priority: Major Reporter: Daniel Stratton Prior to version 2 of the plugin, the JCL that was submitted allowed for variable substitution within the job. We used this extensively (generating timestamps, starting/stopping configurable CICS regions, etc) in the JCL that we have and were running on a regular basis. I can't think of a simple way to replicate this. The best I can think of is an intermediate step from checkout to injection where a shell or command script is run to perform the substitutions prior to the submission. But this feels a bit awkward, and error prone. I'd really like to see this functionality restored, if possible. Happy to look into it myself, just might take a while. Add Comment
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title Dik Rana resolved as Fixed Jenkins / JENKINS-55460 Cleaning of svn workspace broken in 2.157 Change By: Dik Rana 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-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title Dik Rana commented on JENKINS-55460 Re: Cleaning of svn workspace broken in 2.157 Revert of the Util.java in JENKINS-55448 has fixed this issue. The plugin will work in 2.159 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-55418) Pipeline Syntax generator not present
Title: Message Title Ulli Hafner edited a comment on JENKINS-55418 Re: Pipeline Syntax generator not present Could it be that you are looking at '*[Declarative Directive Generator|http://localhost:8080/view/White%20Mountains/job/New%20-%20Pipeline%20Parallel%20-%20Model/directive-generator]'* and not at [Snippet Generator?|http://localhost:8080/view/White%20Mountains/job/New%20-%20Pipeline%20Parallel%20-%20Model/pipeline-syntax] I added a screenshot of the view I am referring to. 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-55418) Pipeline Syntax generator not present
Title: Message Title Ulli Hafner edited a comment on JENKINS-55418 Re: Pipeline Syntax generator not present Could it be that you are looking at '*[Declarative Directive Generator|http://localhost:8080/view/White%20Mountains/job/New%20-%20Pipeline%20Parallel%20-%20Model/directive-generator]'* and not at [Snippet Generator?|http://localhost:8080/view/White%20Mountains/job/New%20-%20Pipeline%20Parallel%20-%20Model/pipeline-syntax] I added a screenshot of the view I am referring to. !Bildschirmfoto 2019-01-16 um 00.39.17.png|thumbnail! 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-55418) Pipeline Syntax generator not present
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55418 Pipeline Syntax generator not present Change By: Ulli Hafner Attachment: Bildschirmfoto 2019-01-16 um 00.39.17.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-55418) Pipeline Syntax generator not present
Title: Message Title Ulli Hafner commented on JENKINS-55418 Re: Pipeline Syntax generator not present Could it be that you are looking at 'Declarative Directive Generator' and not at Snippet Generator? 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-55368) No issues found when parsing Eclipse ECJ output from console log during maven build
Title: Message Title Ulli Hafner updated JENKINS-55368 Jenkins / JENKINS-55368 No issues found when parsing Eclipse ECJ output from console log during maven build Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55418) Pipeline Syntax generator not present
Title: Message Title Andrew Gray commented on JENKINS-55418 Re: Pipeline Syntax generator not present You are correct. Steps -> Sample Step. Option selected is "step: General Build Step". In the secondary "Build Step" drop down list I don’t see a "RecordIssues" option. It looks like you have marked the old ones as deprecated but are yet to provide a syntax generator for the new syntax. 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner updated JENKINS-55357 Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55340) warnings-ng: pylint parser should use new-style labels
Title: Message Title Ulli Hafner updated JENKINS-55340 Jenkins / JENKINS-55340 warnings-ng: pylint parser should use new-style labels Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55337) MavenConsole tool reports errors with dead links.
Title: Message Title Ulli Hafner updated JENKINS-55337 Jenkins / JENKINS-55337 MavenConsole tool reports errors with dead links. Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55513) 'No data available in table' can be improved to 'Loading' while the data is still being loaded
Title: Message Title Ulli Hafner updated JENKINS-55513 Jenkins / JENKINS-55513 'No data available in table' can be improved to 'Loading' while the data is still being loaded Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55495) Improve layout of fixed issues table
Title: Message Title Ulli Hafner updated JENKINS-55495 Jenkins / JENKINS-55495 Improve layout of fixed issues table Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-50096) Integrate http://prismjs.com/ to visualize source code
Title: Message Title Ulli Hafner updated JENKINS-50096 Jenkins / JENKINS-50096 Integrate http://prismjs.com/ to visualize source code Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-25278) Plugin slow parsing Maven warnings
Title: Message Title Ulli Hafner updated JENKINS-25278 Jenkins / JENKINS-25278 Plugin slow parsing Maven warnings Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55358) No issues found when parsing Eclipse ECJ output from console log during an ant build
Title: Message Title Ulli Hafner updated JENKINS-55358 Jenkins / JENKINS-55358 No issues found when parsing Eclipse ECJ output from console log during an ant build Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55514) FindBugs analyzer reports incorrect priority
Title: Message Title Ulli Hafner updated JENKINS-55514 Jenkins / JENKINS-55514 FindBugs analyzer reports incorrect priority Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55511) Using maven compiler and no issues are returned
Title: Message Title Ulli Hafner updated JENKINS-55511 Jenkins / JENKINS-55511 Using maven compiler and no issues are returned Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-22337) Support highlighting of non Java files
Title: Message Title Ulli Hafner updated JENKINS-22337 Jenkins / JENKINS-22337 Support highlighting of non Java files Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55373) Warnings Next Generation: Error on accessing 'MSBUILD' file
Title: Message Title Ulli Hafner updated JENKINS-55373 Jenkins / JENKINS-55373 Warnings Next Generation: Error on accessing 'MSBUILD' file Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.0.0, analysis-model-api 2.0.0 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-55584) Allow generating a report file from 'Static Analysis' aggregated results
Title: Message Title Connor Cook commented on JENKINS-55584 Re: Allow generating a report file from 'Static Analysis' aggregated results That looks like it should fulfill my needs, I just didn't see it when I was looking. Thank you! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55584) Allow generating a report file from 'Static Analysis' aggregated results
Title: Message Title Connor Cook closed an issue as Fixed Jenkins / JENKINS-55584 Allow generating a report file from 'Static Analysis' aggregated results Change By: Connor Cook 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-55608) Log audit event for build start
Title: Message Title David Olorundare assigned an issue to Unassigned Jenkins / JENKINS-55608 Log audit event for build start 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Marky Jackson commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Ok, let me reproduce 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I attached a segment with all the calls related to a failed build that showed this error. 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-55608) Log audit event for build start
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-55608 Log audit event for build start Issue Type: Task Assignee: David Olorundare Components: audit-log-plugin Created: 2019-01-15 22:39 Priority: Minor Reporter: Matt Sicker An event should be logged for when a build is started. Information that I'd like to see: Who started the build (can be either a Jenkins user or an SCM user) Other info from the Cause Project name Build number Timestamp We might determine more data to include later on, but this is a good starting point. Add Comment
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous updated an issue Jenkins / JENKINS-55392 java.util.concurrent.RejectedExecutionException AGAIN Change By: Daniel Watrous Attachment: kube-apiserver-k8s-master-0.app-ui-build-common-27bd2dc4.txt 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-54089) Create an audit log destination global configuration
Title: Message Title Matt Sicker updated JENKINS-54089 Merged to master. Jenkins / JENKINS-54089 Create an audit log destination global configuration Change By: Matt Sicker Status: In Review 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-52968) Investigate change cache from Guava to Caffeine
Title: Message Title Olivier Lamy assigned an issue to Unassigned Jenkins / JENKINS-52968 Investigate change cache from Guava to Caffeine Change By: Olivier Lamy Assignee: Olivier Lamy 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-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite commented on JENKINS-22795 Re: git plugin cleans workspace on initial clone The log entry you provided which mentions ssh-agent is from the ssh-agent plugin, not from the Jenkins agent. It is unlikely to be related to the deletion of files which exist in the workspace of a job before the first clone into the workspace. This bug report is describing a very specific condition which only exists when the workspace of a job is not empty the very first time that Jenkins uses the workspace. That is quite rare. Freestyle jobs usually create the workspace on the Jenkins agent the first time the job is run, then they reuse that workspace on later execution of the same job. When the workspace is created, it is empty and the deletion that is described in this bug report is harmless. There are Jenkins plugins which will allow Freestyle jobs to write files into the workspace after the job starts and before the git repository is cloned into the workspace. The deletion behavior described here will delete those files that are created in the workspace before the git repository is first cloned. I was trying to suggest earlier that you should confirm that the workspace where the files are being deleted has not been damaged or partially deleted by some other scripts or changes in your environment. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Marky Jackson commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Daniel Watrous Can you provide the output of the logs for the kubeapi pod (kubectl -n kube-system log 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Daniel Watrous commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I have now increased my max connections to 512, but I'm confused about what they are. I get this error when there is only one build pod running with nine containers. The kubernetes API is obviously not saturated, so I don't think this really means connections to the kubernetes API. It seems like a leak scenario, where unused "connections" are not being returned to the pool. Is this like "kubectl exec..." connections? 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-22795) git plugin cleans workspace on initial clone
Title: Message Title
Roy Dahan edited a comment on JENKINS-22795
Re: git plugin cleans workspace on initial clone
I don't know if it's related, but few lines in the log before the delete it seems like the agent is started.It happens every run.(It's not a pipeline job) {code:java} [ssh-agent] Looking for ssh-agent implementation... * 20:02:23 * [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) * 20:02:23 * $ ssh-agent*20:02:24* SSH_AUTH_SOCK=/tmp/ssh-3IVCGhG3LDLW/agent.20456*20:02:24* SSH_AGENT_PID=20458*20:02:24* [ssh-agent] Started. {code}
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-22795) git plugin cleans workspace on initial clone
Title: Message Title Roy Dahan commented on JENKINS-22795 Re: git plugin cleans workspace on initial clone I don't know if it's related, but few lines in the log before the delete it seems like the agent is started. It happens every run. (It's not a pipeline job) [ssh-agent] Looking for ssh-agent implementation...20:02:23 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)20:02:23 $ ssh-agent*20:02:24* SSH_AUTH_SOCK=/tmp/ssh-3IVCGhG3LDLW/agent.20456*20:02:24* SSH_AGENT_PID=20458*20:02:24* [ssh-agent] Started. 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-54770) A new client object is created each time the plugin needs to connection to K8s
Title: Message Title Ryan Campbell commented on JENKINS-54770 Re: A new client object is created each time the plugin needs to connection to K8s This was fixed in 1.13.6 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Vlad Uros commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Thanks Naresh. Any chance to add parameter to hide this as well? Thanks, Vlad 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-24078) Jira Link are not created for ClearCase UCM project
Title: Message Title Nilesh Patel commented on JENKINS-24078 Re: Jira Link are not created for ClearCase UCM project This is not working with my Jenkins Jira Plugin. any idea where to check ? 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-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite commented on JENKINS-22795 Re: git plugin cleans workspace on initial clone Roy Dahan you may want to check the agent where that job is running. The removal of the contents only happens on the initial creation of the workspace, not on later requests to update an existing workspace. Something on the agent running the build may be causing the plugin to believe that it needs to perform a fresh clone rather than performing an incremental update. If you're using a Pipeline, you may also want to check the Pipeline definition that it does not include a separate call to deleteDir(). 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-41660) JIRA Issue linking in build Changelog doesn't work
Title: Message Title Nilesh Patel commented on JENKINS-41660 Re: JIRA Issue linking in build Changelog doesn't work Any luck with 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-22795) git plugin cleans workspace on initial clone
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-22795 git plugin cleans workspace on initial clone Change By: Mark Waite Summary: git plugin always cleans workspace , even when instructed not to on initial clone 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-22795) git plugin always cleans workspace, even when instructed not to
Title: Message Title Roy Dahan edited a comment on JENKINS-22795 Re: git plugin always cleans workspace, even when instructed not to I don't know why we started hitting this lately, but we have the exact same problem.Every time we run a job, it tries to clean the workspace before cloning the repo.It wasn't the behaviour till recently and I'm not sure what has changed.Our job create a directory with some results and when it runs again, it cleans this directory although we didn't want it to. If this was one intention, he one would use the options to clean the workspace. 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-22795) git plugin always cleans workspace, even when instructed not to
Title: Message Title Roy Dahan commented on JENKINS-22795 Re: git plugin always cleans workspace, even when instructed not to I don't know why we started hitting this lately, but we have the exact same problem. Every time we run a job, it tries to clean the workspace before cloning the repo. It wasn't the behaviour till recently and I'm not sure what has changed. Our job create a directory with some results and when it runs again, it cleans this directory although we didn't want it to. If this was one intention, he would use the options to clean the workspace. 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-41218) Provide native systemd unit
Title: Message Title
Eugene Ahmethanov edited a comment on JENKINS-41218
Re: Provide native systemd unit
I'll leave the unit template here for Jenkins within multi-instance tomcat installation, maybe this will be helpful.Only one thing - the internal restart commands like safeRestart or restart cause service to be unavailable since restart command is not correct in such case.{code:java}#/lib/systemd/system/tomcat@.service [Unit]Description=Apache Tomcat service for "%i"After=syslog.target network-online.target[Service]SyslogIdentifier=%iUser=%iGroup=%iPermissionsStartOnly=trueEnvironmentFile=-/etc/sysconfig/%iEnvironment='CATALINA_PID=$MAINPID'ExecStartPre=/bin/bash -c 'systemctl set-environment JAVA_HOME=$(readlink -f /usr/bin/java | sed "s:/bin/java::")'ExecStartPre=/bin/bash -c 'systemctl set-environment CATALINA_HOME=$(readlink -f /usr/bin/tomcat)'ExecStart=@/usr/bin/java \$JAVA_OPTS \$JMX_OPTS \$INSTANCE_OPTS \$CATALINA_OPTS \-Djava.endorsed.dirs=${CATALINA_HOME}/endorsed \-Djava.io.tmpdir=${CATALINA_BASE}/temp \-Dcatalina.base=${CATALINA_BASE} \-Dcatalina.home=${CATALINA_HOME} \-classpath ${CATALINA_HOME}/bin/bootstrap.jar:${CATALINA_HOME}/bin/tomcat-juli.jar \org.apache.catalina.startup.Bootstrap startSuccessExitStatus=143[Install]WantedBy=multi-user.targetAlias=%i.service{code} UPD:Example config file for tomcat@jenkins instance:{code:java}#/etc/sysconfig/jenkinsCATALINA_BASE="/opt/jenkins/app"CATALINA_OPTS="-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager"JAVA_OPTS="-Xms189M -Xmx1514M -XX:MaxDirectMemorySize=378M -XX:-UseConcMarkSweepGC -XX:+UseSerialGC"JMX_OPTS=""INSTANCE_OPTS="-Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true -Djenkins.install.runSetupWizard=false"JENKINS_HOME="/opt/jenkins/data"{code} Regards.
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,
[JIRA] (JENKINS-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Mark Waite commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites Stewart Bryson you can either use the build from my github repository or build it yourself. That build resolves the issues I've seen. 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-41218) Provide native systemd unit
Title: Message Title
Eugene Ahmethanov commented on JENKINS-41218
Re: Provide native systemd unit
I'll leave the unit template here for Jenkins within multi-instance tomcat installation, maybe this will be helpful. Only one thing - the internal restart commands like safeRestart or restart cause service to be unavailable since restart command is not correct in such case.
#/lib/systemd/system/tomcat@.service
[Unit]
Description=Apache Tomcat service for "%i"
After=syslog.target network-online.target
[Service]
SyslogIdentifier=%i
User=%i
Group=%i
PermissionsStartOnly=true
EnvironmentFile=-/etc/sysconfig/%i
Environment='CATALINA_PID=$MAINPID'
ExecStartPre=/bin/bash -c 'systemctl set-environment JAVA_HOME=$(readlink -f /usr/bin/java | sed "s:/bin/java::")'
ExecStartPre=/bin/bash -c 'systemctl set-environment CATALINA_HOME=$(readlink -f /usr/bin/tomcat)'
ExecStart=@/usr/bin/java \
$JAVA_OPTS \
$JMX_OPTS \
$INSTANCE_OPTS \
$CATALINA_OPTS \
-Djava.endorsed.dirs=${CATALINA_HOME}/endorsed \
-Djava.io.tmpdir=${CATALINA_BASE}/temp \
-Dcatalina.base=${CATALINA_BASE} \
-Dcatalina.home=${CATALINA_HOME} \
-classpath ${CATALINA_HOME}/bin/bootstrap.jar:${CATALINA_HOME}/bin/tomcat-juli.jar \
org.apache.catalina.startup.Bootstrap start
SuccessExitStatus=143
[Install]
WantedBy=multi-user.target
Alias=%i.service
Regards.
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-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title boris ivan updated an issue Jenkins / JENKINS-55605 can only click on the first active parallel stage, others running but cannot click Change By: boris ivan I have a pipeline with parallel sequential stages (the same problem might occur if there are parallel 1-stage, not sure) and can only click on the first 'active' stage. Too much to obfuscate, will do ascii: 4 parallel - sequential stages below: r--- s1 --- | . |--- s2 --- | . |--- s3 — ... s4 ... | . L--- s5 — s6 s4 and s6 included in the diagram in case it's relevant, but the problem happens without them being shown visually in what I'm about to describe, as those stages haven't started yet:s1 is a single stage and complete (green)s2, s3, s5 all show as animated blue circles, which is accurate. Going out of blue ocean and examining legacy pipeline view properly shows logs progressing on those.But in the blue ocean view, I can only click on s1, or s2, and have the bottom half of the screen (console log, etc) update. s3 and s5 on hover-over show that they're clickable, but clicking them does nothing. Only clicking s1 or s2 changes the context of the bottom half of the blue ocean UI.Potentially of interest:If I'm currently clicked/selected on s2, then clicking s3/s5 does nothing.If I'm currently clicked/selected on s1 (the one that is green/complete), then clicking on s3/s5 changes the bottom context to *s2*.It's as is clicking on any active parallel stage will only set the bottom context to the first _active_ parallel stage, but that is just a guess.As I write this – the graph has now progressed so that s2, s4, and s6 are active. s1, s3, and s5 are complete. Still has the same problem – if I click on s4 or s6, it only shows the context of s2. Add Comment
[JIRA] (JENKINS-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title boris ivan created an issue Jenkins / JENKINS-55605 can only click on the first active parallel stage, others running but cannot click Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-01-15 19:24 Environment: blueocean 1.10.1, all browsers Priority: Major Reporter: boris ivan I have a pipeline with parallel sequential stages (the same problem might occur if there are parallel 1-stage, not sure) and can only click on the first 'active' stage. Too much to obfuscate, will do ascii: r--s1-- --s2--
[JIRA] (JENKINS-55215) Log from cmake/ctest steps isn't fully captured on OsX
Title: Message Title Martin Weber assigned an issue to Unassigned Jenkins / JENKINS-55215 Log from cmake/ctest steps isn't fully captured on OsX Change By: Martin Weber Assignee: Martin Weber 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging I have added those log statements explicitly to note the actual command being run, it was intentional, otherwise there would be no clue about the command being run. 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-55604) EnvVars.expand not working recursively
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-55604 EnvVars.expand not working recursively Change By: Jesse Glick Assignee: Jesse Glick 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-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title
Stewart Bryson edited a comment on JENKINS-50715
Re: Pipeline fails with NPE due to Blue Ocean favorites
I get this with every single PR I open. And it only started in the last month... so I'm not exactly sure if it's related to this thread which was opened months ago. But... the error stack is exactly the same, which you can see below.Jenkins: 2.159 Blue Ocean: 1.10.1Autofavoriate: 1.2.2 Are people just dealing with this? I'm seriously looking at dumping Jenkins for this. Every single PR fails until I run it manually the first time.{code:java}java.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:70) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:120) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
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-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title
Stewart Bryson edited a comment on JENKINS-50715
Re: Pipeline fails with NPE due to Blue Ocean favorites
I get this with every single PR I open. And it only started in the last month... so I'm not exactly sure if it's related to this thread which was opened months ago. But... there the error stack is exactly the same, which you can see below. Jenkins: 2.159 Are people just dealing with this? I'm seriously looking at dumping Jenkins for this. Every single PR fails until I run it manually the first time.{code:java}java.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:70) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:120) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum updated JENKINS-46507 Jenkins / JENKINS-46507 Parallel Pipeline random java.lang.InterruptedException 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-50715) Pipeline fails with NPE due to Blue Ocean favorites
Title: Message Title Stewart Bryson commented on JENKINS-50715 Re: Pipeline fails with NPE due to Blue Ocean favorites I get this with every single PR I open. And it only started in the last month... so I'm not exactly sure if it's related to this thread which was opened months ago. But... there error stack is exactly the same, which you can see below. Are people just dealing with this? I'm seriously looking at dumping Jenkins for this. Every single PR fails until I run it manually the first time. java.lang.NullPointerException at io.jenkins.blueocean.autofavorite.FavoritingScmListener.onCheckout(FavoritingScmListener.java:70) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:136) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:120) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:293) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE 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-55604) EnvVars.expand not working recursively
Title: Message Title Rob Long assigned an issue to Jesse Glick Jenkins / JENKINS-55604 EnvVars.expand not working recursively Change By: Rob Long Assignee: Jesse Glick 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-55604) EnvVars.expand not working recursively
Title: Message Title
Rob Long created an issue
Jenkins / JENKINS-55604
EnvVars.expand not working recursively
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-01-15 18:19
Priority:
Major
Reporter:
Rob Long
Global properties that reference other global properties are only partially expanded by EnvVars.expand() Reproduce steps:
Define global property INNER with value Foo
Defined global property OUTER with value $INNER/Bar
Create a FreeStyle project with a System Groovy build step containing the following code:
println build.getEnvironment(listener).expand('${OUTER}');
Expected output is: Foo/Bar Actual output is: $INNER/Bar Performing same test on Jenkins v 1.625 results in correct output. Not sure when it changes as I'm currently upgrading systems from 1.625 to 2.150
[JIRA] (JENKINS-55603) ParameterizedRemoteTrigger Plugin returning 401 when connecting to remote Jenkins server
Title: Message Title Conor Smyth updated an issue Jenkins / JENKINS-55603 ParameterizedRemoteTrigger Plugin returning 401 when connecting to remote Jenkins server Change By: Conor Smyth When trying to use the ParameterizedRemoteTrigger plugin from one Jenkins server to execute a job on a remote Jenkins server using a Groovy script, the Jenkins job returns a 401 unauthorized exception.Exception Message: "Connection to remote server failed [401], waiting for to retry - 15 seconds until next attempt."Using the CredentialsAuth(credentialsId: '') with a user that can sign into the remote server using a username and password.Function used in Groovy script: 'org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep'( )Not sure if it is relevant but the job URL string has spaces in the job name which are encoded. 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Konstantin Bläsi commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Seeing this with Jenkins 2.150.1 and Kubernetes Plugin 1.14.3. Jenkins restart does help, but is not useful enough because the issue is back very soon. Are there any details on this issue already? Any tip for debugging 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-6368) SVN plugin is not supported by github.com
Title: Message Title Bryce Schober commented on JENKINS-6368 Re: SVN plugin is not supported by github.com In case others happen to come by here, I accidentally discovered a "work-around" to this problem. My actual usage gets around this issue somehow, since it only uses the GitHub project as sub-project in an svn:external. The root project is from a private ordinary subversion server. It may also make a difference that the job is now run in a Docker container, and Jenkins appears to do the SCM polling operations in the container. If it were important enough, one could try a trivial "wrapper" project on a private SVN server or a free online SVN server that contained only the github-svn external. 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-55603) ParameterizedRemoteTrigger Plugin returning 401 when connecting to remote Jenkins server
Title: Message Title Conor Smyth created an issue Jenkins / JENKINS-55603 ParameterizedRemoteTrigger Plugin returning 401 when connecting to remote Jenkins server Issue Type: Bug Assignee: KaiHsiang Chang Components: parameterized-remote-trigger-plugin Created: 2019-01-15 17:27 Environment: Production Priority: Minor Reporter: Conor Smyth When trying to use the ParameterizedRemoteTrigger plugin from one Jenkins server to execute a job on a remote Jenkins server using a Groovy script, the Jenkins job returns a 401 unauthorized exception. Exception Message: "Connection to remote server failed [401], waiting for to retry - 15 seconds until next attempt." Using the CredentialsAuth(credentialsId: '') with a user that can sign into the remote server using a username and password. Function used in Groovy script: 'org.jenkinsci.plugins.ParameterizedRemoteTrigger.pipeline.RemoteBuildPipelineStep'( Add Comment
[JIRA] (JENKINS-55602) GitHub shows user's icon in check status instead of Jenkins one
Title: Message Title Vitaly Karasik created an issue Jenkins / JENKINS-55602 GitHub shows user's icon in check status instead of Jenkins one Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-15 17:06 Priority: Minor Reporter: Vitaly Karasik Into "Branch Sources" GitHub credentials we use my Github personal token. The problem that all Jenkins statuses are marked by my user's icon. Where/How I can modify this icon to some system, not 'personal' one? Add Comment
[JIRA] (JENKINS-55601) Update documentation with links to JIRA Issue Tracking
Title: Message Title Mark Symons created an issue Jenkins / JENKINS-55601 Update documentation with links to JIRA Issue Tracking Issue Type: Improvement Assignee: Steve Springett Components: dependency-track-plugin Created: 2019-01-15 15:55 Labels: documentation Priority: Minor Reporter: Mark Symons Update README.md with a link to JIRA. Additionally, add link to plugin listing. Perhaps to external references section? Suggest tweaking the link so that it filters by the the link by the dependency-track-plugin component: https://issues.jenkins-ci.org/issues/?jql=component%20%3D%20dependency-track-plugin This would provide visibility into what issues have already been logged. Add Comment
[JIRA] (JENKINS-55478) CompositeIOException when deleting workspace before check-out
Title: Message Title Matt Sicker commented on JENKINS-55478 Re: CompositeIOException when deleting workspace before check-out Yes, we reverted the problem, and I have updated code for the original problem to be merged for the next weekly release. 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-55561) Stages within stage thoriwng error
Title: Message Title Vivek Pandey commented on JENKINS-55561 Re: Stages within stage thoriwng error Shivu R H Please attach pipeline code thats causing this error. 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-55333) Add Deployment feature for Tomcat 9
Title: Message Title Nitinkumar Thakkar commented on JENKINS-55333 Re: Add Deployment feature for Tomcat 9 Davi Junior and Oleg Nenashev Do you know by when will the adapter created? or the schedule release for this improvement? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27301) Pipeline support for XTrigger
Title: Message Title Bhanu Pathak commented on JENKINS-27301 Re: Pipeline support for XTrigger Kinldy fix this issue if possible or atleast provide some pointers how it can be implemented 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-51170) Workflowstep-specific environment variables
Title: Message Title Devin Nusbaum updated JENKINS-51170 Jenkins / JENKINS-51170 Workflowstep-specific environment variables 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-55096) can not override jnlp container
Title: Message Title Carlos Sanchez commented on JENKINS-55096 Re: can not override jnlp container logs please https://github.com/jenkinsci/kubernetes-plugin/#debugging 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Andrew a No problem! I will move forward with my PR (adding an additional timeout), thanks so much for interactively debugging the 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-55096) can not override jnlp container
Title: Message Title
Dmitry commented on JENKINS-55096
Re: can not override jnlp container
Update: I've upgraded Jenkins version to the 2.150.1 and plugin to 1.14.3, now I was able to override jnlp container image, but podTemplate inheritance is still broken, my settings are: The pipeline code is:
podTemplate(label: 'myPod', inheritFrom: 'defaultpod', containers: [
containerTemplate(name: 'jnlp', image: 'mycustomimage'),
containerTemplate(name: 'golang', image: 'golang:1.8.0', ttyEnabled: true, command: 'cat')
]) {
node('myPod') {
but the pod template I get in k8s doesn't has TEST_VAR variable defined
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-55096) can not override jnlp container
Title: Message Title Dmitry updated an issue Jenkins / JENKINS-55096 can not override jnlp container Change By: Dmitry Attachment: image-2019-01-15-17-13-06-625.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-55096) can not override jnlp container
Title: Message Title Dmitry updated an issue Jenkins / JENKINS-55096 can not override jnlp container Change By: Dmitry Attachment: image-2019-01-15-17-12-54-166.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-55592) GIT_COMMIT contains unknown value
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55592 GIT_COMMIT contains unknown value Change By: Mark Waite Assignee: Mark Waite 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-55592) GIT_COMMIT contains unknown value
Title: Message Title Mark Waite commented on JENKINS-55592 Re: GIT_COMMIT contains unknown value Since you're using a shared library, the initial checkout of the repository for the Jenkinsfile is followed by a checkout of the shared library and then may be followed by the merge. Each of those three operations has a SHA1. I suspect that is the SHA1 hash of the HEAD of the shared library. Can you confirm that? You may need to use the shell / bat technique to get the SHA1 of the HEAD of the workspace. Refer to getSHA1 as an example to do that. 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-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title
Alexandr Panshin edited a comment on JENKINS-55600
Re: Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Though I still guess it is a defect (I suppose "labelParameters = []" instruction in Groovy should rewrite pointer value?), this problem seems to appear because of using same "labelParameters" variable for all of jobs. Using separate Instantiating container for parameters for each job seems to solve the problem:{code:java}pipeline {agent nonestages {stage('Processing projects') {steps {script {def projects = ['project0', 'project1', 'project2', 'project3', 'project4']def projectsBuilds = [:] // essential change herefor (project in projects) { //JENKINS-55426 need to save iterated variable value into intermediate variable, otherwise there will be last value from collection for all jobs def currentProject = project def labelParameters = [] labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux']) labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: currentProject]) projectsBuilds[currentProject] = { stage(String.format('%s execution', currentProject)) { build job: 'Sample-Job', parameters: labelParameters } }}print(projectsBuilds)parallel projectsBuilds;}}}}}{code}
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
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title
Alexandr Panshin commented on JENKINS-55600
Re: Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Though I still guess it is a defect (I suppose "labelParameters = []" instruction in Groovy should rewrite pointer value?), this problem seems to appear because of using same "labelParameters" variable for all of jobs. Using separate container for parameters for each job seems to solve the problem:
pipeline {
agent none
stages {
stage('Processing projects') {
steps {
script {
def projects = ['project0', 'project1', 'project2', 'project3', 'project4']
def projectsBuilds = [:] // essential change here
for (project in projects) {
//JENKINS-55426 need to save iterated variable value into intermediate variable, otherwise there will be last value from collection for all jobs
def currentProject = project
def labelParameters = []
labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])
labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: currentProject])
projectsBuilds[currentProject] = {
stage(String.format('%s execution', currentProject)) {
build job: 'Sample-Job', parameters: labelParameters
}
}
}
print(projectsBuilds)
parallel projectsBuilds;
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title
Alexandr Panshin updated an issue
Jenkins / JENKINS-55600
Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Change By:
Alexandr Panshin
1) I created sample job (see "sample_job_config.xml" attachment) which has "PROJECT_NAME" parameter 2) I want to run it in parallel 5 times with different "PROJECT_NAME" values. I created following script for this:{code:java}pipeline {agent nonestages {stage('Processing projects') {steps {script {def projectsBuilds projects = [ :]def labelParameters = []labelParameters.add([$class: ' LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: ' project0' ])projectsBuilds['project0'] = { stage(String.format('%s execution' , ' project0 project1 ' )) { build job: 'Sample-Job' , parameters: labelParameters }}labelParameters = []labelParameters.add([$class: ' LabelParameterValue project2 ', name: ' node project3 ', label: ' linux project4 '] ) labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project1']) def projectsBuilds ['project1'] = { stage(String.format('%s execution', 'project1')) { build job: 'Sample-Job', parameters: labelParameters }}labelParameters = [ ]labelParameters.add([$class : 'LabelParameterValue', name: 'node', label: 'linux' ] ) def labelParameters .add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project2']) projectsBuilds['project2'] = { stage for ( String.format('%s execution', 'project2' project in projects ) ) { build job: 'Sample //JENKINS - Job' 55426 need to save iterated variable value into intermediate variable , parameters: labelParameters }}labelParameters = []labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", otherwise there will be last value : 'project3']) from collection for all jobs projectsBuilds['project3'] def currentProject = { project stage(String.format('%s execution', 'project3')) { build job: 'Sample-Job', parameters: labelParameters }}labelParameters = []
[JIRA] (JENKINS-55442) Need filter by message text
Title: Message Title Simon M commented on JENKINS-55442 Re: Need filter by message text I agree that filtering based on the message text would be helpful. E.g. I don't care for documentation warnings from the unit tests, but I still want to get compiler warnings from the unit tests. Right now I can only filter on the category (which doesn't because for documentation warnings here it's "Warning") or on the file name (but I still want the compiler warnings). The old warnings plugin had this feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title Alexandr Panshin updated an issue Jenkins / JENKINS-55600 Parallel execution of same job N times with different parameters leads to only 1 execution of the job Change By: Alexandr Panshin Priority: Major Minor 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-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title Alexandr Panshin updated an issue Jenkins / JENKINS-55600 Parallel execution of same job N times with different parameters leads to only 1 execution of the job Change By: Alexandr Panshin Attachment: screen.jpg 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-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title
Alexandr Panshin updated an issue
Jenkins / JENKINS-55600
Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Change By:
Alexandr Panshin
1) I created sample job (see "sample_job_config.xml" attachment) which has "PROJECT_NAME" parameter2) I want to run it in parallel 5 times with different "PROJECT_NAME" values. I created following script for this: {code:java}pipeline {agent nonestages {stage('Processing projects') {steps {script {def projectsBuilds = [:]def labelParameters = []labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project0'])projectsBuilds['project0'] = { stage(String.format('%s execution', 'project0')) { build job: 'Sample-Job', parameters: labelParameters }}labelParameters = []labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project1'])projectsBuilds['project1'] = { stage(String.format('%s execution', 'project1')) { build job: 'Sample-Job', parameters: labelParameters }}labelParameters = []labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project2'])projectsBuilds['project2'] = { stage(String.format('%s execution', 'project2')) { build job: 'Sample-Job', parameters: labelParameters }}labelParameters = []labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project3'])projectsBuilds['project3'] = { stage(String.format('%s execution', 'project3')) { build job: 'Sample-Job', parameters: labelParameters }}labelParameters = []labelParameters.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project4'])projectsBuilds['project4'] = { stage(String.format('%s execution', 'project4')) { build job: 'Sample-Job', parameters: labelParameters }
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title
Alexandr Panshin updated an issue
Jenkins / JENKINS-55600
Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Change By:
Alexandr Panshin
Summary:
Parallel execution of same job N times with different parameters leads to only 2 executions 1 execution of the job
1) I created sample job (see "sample_job_config.xml" attachment) which has "PROJECT_NAME" parameter2) I want to run it in parallel 5 times with different "PROJECT_NAME" values. I created following script for this:{code:java}pipeline {agent nonestages {stage('Processing projects') {steps {script {def projectsBuilds = [:]def labelParameters0 labelParameters = [] labelParameters0 labelParameters .add([$class: 'LabelParameterValue', name: 'node', label: 'linux']) labelParameters0 labelParameters .add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project0'])projectsBuilds['project0'] = { stage(String.format('%s execution', 'project0')) { build job: 'Sample-Job', parameters: labelParameters0 labelParameters }} def labelParameters1 labelParameters = [] labelParameters0 labelParameters .add([$class: 'LabelParameterValue', name: 'node', label: 'linux']) labelParameters0 labelParameters .add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project1'])projectsBuilds['project1'] = { stage(String.format('%s execution', 'project1')) { build job: 'Sample-Job', parameters: labelParameters1 labelParameters }} def labelParameters2 labelParameters = [] labelParameters0 labelParameters .add([$class: 'LabelParameterValue', name: 'node', label: 'linux']) labelParameters0 labelParameters .add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project2'])projectsBuilds['project2'] = { stage(String.format('%s execution', 'project2')) { build job: 'Sample-Job', parameters: labelParameters2 labelParameters }} def labelParameters3 labelParameters = [] labelParameters0 labelParameters .add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title Alexandr Panshin updated an issue Jenkins / JENKINS-55600 Parallel execution of same job N times with different parameters leads to only 1 execution of the job Change By: Alexandr Panshin Attachment: screen0.jpg 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-55600) Parallel execution of same job N times with different parameters leads to only 1 execution of the job
Title: Message Title Alexandr Panshin updated an issue Jenkins / JENKINS-55600 Parallel execution of same job N times with different parameters leads to only 1 execution of the job Change By: Alexandr Panshin Attachment: screen1.jpg 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-51745) Wrong elapsed time showing in blueocean
Title: Message Title kutzi commented on JENKINS-51745 Re: Wrong elapsed time showing in blueocean Actually, both are often shown wrong for me: duration of single steps and duration for the whole pipeline. And it's always that the shown time is to long. 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-48859) BlueOcean API parallel node duration in ms incorrect in declarative pipeline
Title: Message Title kutzi commented on JENKINS-48859 Re: BlueOcean API parallel node duration in ms incorrect in declarative pipeline Is there any update on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 2 executions of the job
Title: Message Title
Alexandr Panshin updated an issue
Jenkins / JENKINS-55600
Parallel execution of same job N times with different parameters leads to only 2 executions of the job
Change By:
Alexandr Panshin
# 1) I created sample job (see "sample_job_config.xml" attachment) which has "PROJECT_NAME" parameter # 2) I want to run it in parallel 5 times with different "PROJECT_NAME" values. I created following script for this:{code:java}pipeline {agent nonestages {stage('Processing projects') {steps {script {def projectsBuilds = [:]def labelParameters0 = []labelParameters0.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters0.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project0'])projectsBuilds['project0'] = { stage(String.format('%s execution', 'project0')) { build job: 'Sample-Job', parameters: labelParameters0 }}def labelParameters1 = []labelParameters0.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters0.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project1'])projectsBuilds['project1'] = { stage(String.format('%s execution', 'project1')) { build job: 'Sample-Job', parameters: labelParameters1 }}def labelParameters2 = []labelParameters0.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters0.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project2'])projectsBuilds['project2'] = { stage(String.format('%s execution', 'project2')) { build job: 'Sample-Job', parameters: labelParameters2 }}def labelParameters3 = []labelParameters0.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters0.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project3'])projectsBuilds['project3'] = { stage(String.format('%s execution', 'project3')) { build job: 'Sample-Job', parameters: labelParameters3 }}def labelParameters4 = []labelParameters0.add([$class: 'LabelParameterValue', name: 'node', label: 'linux'])labelParameters0.add([$class: "StringParameterValue", name: "PROJECT_NAME", value: 'project4'])projectsBuilds['project4'] = { stage(String.format('%s execution', 'project4')) { build job: 'Sample-Job',
[JIRA] (JENKINS-55600) Parallel execution of same job N times with different parameters leads to only 2 executions of the job
Title: Message Title
Alexandr Panshin created an issue
Jenkins / JENKINS-55600
Parallel execution of same job N times with different parameters leads to only 2 executions of the job
Issue Type:
Bug
Assignee:
vjuranek
Attachments:
sample_job_config.xml, screen0.jpg, screen1.jpg
Components:
groovy-plugin
Created:
2019-01-15 13:37
Environment:
Jenkins 2.150.1, Pipeline-Groovy Plugin 2.57
Labels:
groovy parallel
Priority:
Major
Reporter:
Alexandr Panshin
I created sample job (see "sample_job_config.xml" attachment) which has "PROJECT_NAME" parameter
I want to run it in parallel 5 times with different "PROJECT_NAME" values. I created following script for this:
pipeline {
agent none
stages {
stage('Processing projects') {
steps {
script {
def projectsBuilds = [:]
def labelParameters0 = []
labelParameters0.add([$class: 'LabelParameterValue',
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Louis Heche commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError I had the same problem, and we fixed it by allowing more stack to the each thread of the JVM. You can do that by modifying the Jenkins.xml file, add the parameter -Xss with the size of the stack you want to allow to each thread 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.
