[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title Allan C edited a comment on JENKINS-56594 Re: Warnings trend graph has no y-axis legend [~drulli] Hi Ulli. Hope you are safe and sound. [~wlodkowc] and I haven't have been working on this remotely. We created a boolean method in JobAction class to iterate through all previous results, and check if the number of warnings is 0. Now we are trying to test this new method. We found JobActionITest.java but it does not seem to be a proper test class for us. Do you mind sharing some of your insights? Should we create our own test class, or is there one available that we are not aware of? If we do need to create a new test class, what is the simplest way to create a build result with different numbers of warnings and errors? Thank you and take care. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198216.1552902109000.9510.1586746080411%40Atlassian.JIRA.
[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit
Title: Message Title Mark Waite edited a comment on JENKINS-61861 Re: Jenkins Job is Triggering twice for a single Commit I listed the items you'll need to provide [~anvesh1402] in my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-61861?focusedCommentId=388825=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-388825]. Based on the information you've provided since then, you'll also need to describe the following items:* Numbered list of steps the user performs which will show the problem on a newly installed Jenkins (not provided yet)* Type of Jenkins job with the config.xml of the job (not provided yet)* Type of SCM system used and whether the repository is public or private (not provided yet)* Type of status notification system configured for the repository (web hooks, notifyCommit, polling, etc.) (not provided yet)* Contents of a Jenkins support bundle from the support core plugin so that plugin versions are noted and Jenkins configuration is provided (not provided yet, may not be possible with that ancient Jenkins version, then will need to provide the same information without using the support core plugin)* Can you see the same problem on a current Jenkins version (2.222.1) with current plugins (git plugin 4.2.2, git client plugin 3.2.1) (not provided yet) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the
[JIRA] (JENKINS-61876) Add an `includes` directive to matrix
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-61876 Add an `includes` directive to matrix Issue Type: Improvement Assignee: Liam Newman Components: pipeline-model-definition-plugin Created: 2020-04-12 20:31 Priority: Minor Reporter: Liam Newman This reddit question has convinced me that we need an "includes" directive for matrix. User wanted a very sparse matrix: Arch Platform OS Variant Device Debug aarch64 pine64 mobile pinephone y aarch64 pine64 mobile
[JIRA] (JENKINS-51197) Auto-Installation does not work if latest build-tools are an RC version
Title: Message Title Nikolas Falco updated JENKINS-51197 Jenkins / JENKINS-51197 Auto-Installation does not work if latest build-tools are an RC version Change By: Nikolas Falco Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190511.1525773667000.9486.1586721480232%40Atlassian.JIRA.
[JIRA] (JENKINS-51197) Auto-Installation does not work if latest build-tools are an RC version
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-51197 Auto-Installation does not work if latest build-tools are an RC version Change By: Nikolas Falco Assignee: Michael Musenbrock Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190511.1525773667000.9484.1586718180170%40Atlassian.JIRA.
[JIRA] (JENKINS-61594) Getting exception when running Micro Focus Plugin for Performance Center Git Integration
Title: Message Title Daniel Danan started work on JENKINS-61594 Change By: Daniel Danan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205291.1584650208000.9482.1586707748414%40Atlassian.JIRA.
[JIRA] (JENKINS-61594) Getting exception when running Micro Focus Plugin for Performance Center Git Integration
Title: Message Title Daniel Danan commented on JENKINS-61594 Re: Getting exception when running Micro Focus Plugin for Performance Center Git Integration Hi Chris, I have this plugin installed on Jenkins ver. 2.202 and it works fine there. Perhaps i could getting the stack trace of the error could help. Please activate the logs of the plugin in debug: From Jenkins Home page, navigate o Manage Jenkins -> Configure System -> Find the section "Micro Focus LoadRunner Enterprise Integration" or "Micro Focus Performance Center Integration" and switch the debug checkbox on, then run the job once again. Send me the stack trace of the failure reported in the logs. Hopefully, this will help me locate the exact line of code that is failing and understand the reason it fails for you. regards, Daniel Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205291.1584650208000.9480.1586707748384%40Atlassian.JIRA.
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title Roman Bober commented on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator having same issue with spread operator in my jenkins pipeline Are there any solution for this? org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 69: spread not yet supported for CPS transformation @ line 69, column 63. build_windows_project(*(build_wi ^ 1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:133) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:126) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320) 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.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title Roman Bober edited a comment on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator having same issue with spread operator( \ *) in my jenkins pipelineAre there any solution for this? org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 69: spread not yet supported for CPS transformation @ line 69, column 63. build_windows_project(*(build_wi ^1 errorat org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:133) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:126) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320) 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.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title Roman Bober edited a comment on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator having same issue with spread operator ( \ *) in my jenkins pipeline Are Is there any solution for this? org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 69: spread not yet supported for CPS transformation @ line 69, column 63. build_windows_project(*(build_wi ^1 errorat org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:133) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:126) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320) 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.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title rakesh kumar created an issue Jenkins / JENKINS-61875 Run an jenkins stage with an merge commit message using jenkinsfile Issue Type: Task Assignee: Unassigned Components: jenkinsfile-runner Created: 2020-04-12 14:02 Environment: qa Priority: Blocker Reporter: rakesh kumar Run an jenkins stage with an merge commit message using jenkinsfile currently I have built an jenkinsfile with all the stages enabled but i need to add an _expression_ (suitably WHEN) into it which would trigger a particular stage when I merge my code in github with merge commit message RELEASE. Add Comment
[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit
Title: Message Title Mark Waite commented on JENKINS-61861 Re: Jenkins Job is Triggering twice for a single Commit I listed the items you'll need to provide Anvesh Ramaswamy in my earlier comment. Based on the information you've provided since then, you'll also need to describe the following items: Numbered list of steps the user performs which will show the problem on a newly installed Jenkins (not provided yet) Type of Jenkins job with the config.xml of the job (not provided yet) Type of SCM system used and whether the repository is public or private (not provided yet) Type of status notification system configured for the repository (web hooks, notifyCommit, polling, etc.) (not provided yet) Contents of a Jenkins support bundle from the support core plugin so that plugin versions are noted and Jenkins configuration is provided (not provided yet, may not be possible with that ancient Jenkins version, then will need to provide the same information without using the support core plugin) Can you see the same problem on a current Jenkins version (2.222.1) with current plugins (git plugin 4.2.2, git client plugin 3.2.1) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61861) Jenkins Job is Triggering twice for a single Commit
Title: Message Title Anvesh Ramaswamy commented on JENKINS-61861 Re: Jenkins Job is Triggering twice for a single Commit Hi Mark, could you please help me in detail, what are the thing you require to investigate the issue. Kindly help me on this please Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205725.1586498472000.9451.1586698140165%40Atlassian.JIRA.
[JIRA] (JENKINS-56452) Test results not shown for matrix job
Title: Message Title Nikolas Falco commented on JENKINS-56452 Re: Test results not shown for matrix job xunit plugin uses delegates the processed transformed report to junit plugin and use its function to publish the trend report. So it do not nothing more. Maybe in matrix plugin that do something specialized in this case. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198049.1551934672000.9448.1586685720210%40Atlassian.JIRA.
[JIRA] (JENKINS-59979) Script Security: JCasC ScriptApproval does not apply until Jenkins reboot
Title: Message Title akostadinov commented on JENKINS-59979 Re: Script Security: JCasC ScriptApproval does not apply until Jenkins reboot For me it worked properly on Jenkins 2.190, casc plugin 1.36 and Script Security plugin 1.68. security: scriptApproval: approvedSignatures: - method java.net.URI getHost Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202784.1572381545000.9445.1586685600278%40Atlassian.JIRA.
