[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title James Howe commented on JENKINS-60044 Re: mavenConsole tool doesn't extract compile warnings Well that's why I didn't add the Java parser, because I'm using Maven, which has a different output format to javac. Ah well. Solved now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202872.1572887363000.9200.1572950880147%40Atlassian.JIRA.
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title James Howe commented on JENKINS-60044 Re: mavenConsole tool doesn't extract compile warnings Ah, that's quite surprising behaviour. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202872.1572887363000.8558.1572897300248%40Atlassian.JIRA.
[JIRA] (JENKINS-60044) mavenConsole tool doesn't extract compile warnings
Title: Message Title James Howe created an issue Jenkins / JENKINS-60044 mavenConsole tool doesn't extract compile warnings Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2019-11-04-17-08-44-596.png Components: warnings-ng-plugin Created: 2019-11-04 17:09 Environment: Jenkins 2.190.2 Warnings 7.1.0 Maven 3.6.2 Priority: Major Reporter: James Howe I have a build that logs multiple warnings across multiple maven executions. However the warning plugin is only picking up the warnings from add-resource and test, not compile nor testCompile. recordIssues tool: mavenConsole(), qualityGates: [[threshold: 1, type: 'TOTAL', unstable: true]] Console log (abbreviated) [INFO] --- license-maven-plugin:2.0.0:add-third-party (default) @ project --- [WARNING] [WARNING] licenseMerges will be overridden by licenseMergesUrl. [WARNING] [INFO] Writing third-party file to
[JIRA] (JENKINS-58876) System.currentTimeSeconds not found in pipeline
Title: Message Title James Howe commented on JENKINS-58876 Re: System.currentTimeSeconds not found in pipeline It also works in a global pipeline library, but not in a folder pipeline library. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201196.1565362744000.8365.1572872100137%40Atlassian.JIRA.
[JIRA] (JENKINS-59939) durable_task_monitor_1.31_unix_64: no such file or directory
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-59939
durable_task_monitor_1.31_unix_64: no such file or directory
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker, durable-task-plugin, pipeline
Created:
2019-10-25 17:00
Environment:
Jenkins 2.190.1 Docker version 1.13.1, build 8633870/1.13.1 CentOS Linux release 7.7.1908 (Core)
Priority:
Major
Reporter:
James Howe
This just started happening today, but I cannot identify a cause. Pipeline script involving sh inside a Dockerfile agent.
stage('Test') {
agent {
dockerfile {
additionalBuildArgs "--tag jenkins/${dockerName}:${BRANCH_NAME}"
args '--cap-add=SYS_ADMIN'
reuseNode true
}
}
environment {
NG_PORT = PortAllocator.get()
}
steps {
sh 'npm run --silent -- lint --force --format=checkstyle >checkstyle-result.xml'
// ...
Job fails with
process apparently never started in /var/lib/jenkins/node/workspace/JOBNAME@tmp/durable-eb571b59 ... ERROR: script returned exit code -2
The following is in the system log
dockerd-current: time="2019-10-25T17:23:12.299653636+01:00" level=error msg="Error running exec in container: rpc error: code = 2 desc = oci runtime
[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows
Title: Message Title James Howe commented on JENKINS-59867 Re: NodeJS tool installation fails on Windows My guess was something to do with the old MAX_PATH limit, but if it's only Windows 2019 that's more odd. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202606.1571659896000.214.1571913780244%40Atlassian.JIRA.
[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows
Title: Message Title James Howe created an issue Jenkins / JENKINS-59867 NodeJS tool installation fails on Windows Issue Type: Bug Assignee: Nikolas Falco Attachments: image-2019-10-21-13-07-02-606.png Components: nodejs-plugin Created: 2019-10-21 12:11 Environment: Windows Server 2019 (OS Build 17763.678) Labels: windows Priority: Major Reporter: James Howe Tool installation on a Windows node fails for some reason at this rename: Unpacking [https://nodejs.org/dist/v10.16.3/node-v10.16.3-win-x64.zip] to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10 on devops-test3-vm java.io.IOException: Failed to rename C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64 to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64.__rename at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2171) at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2159) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at
[JIRA] (JENKINS-59584) java.io.IOException: Unable to locate binary
Title: Message Title James Howe commented on JENKINS-59584 Re: java.io.IOException: Unable to locate binary Is a "latest available" option for each major version/implementation possible? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202224.1569845119000.9026.1569941460282%40Atlassian.JIRA.
[JIRA] (JENKINS-59584) java.io.IOException: Unable to locate binary
Title: Message Title James Howe commented on JENKINS-59584 Re: java.io.IOException: Unable to locate binary Going further back on the list of available JDKs, jdk-11.0.4+11_openj9-0.15.1 worked. I have no idea why. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202224.1569845119000.7823.1569847020122%40Atlassian.JIRA.
[JIRA] (JENKINS-59584) java.io.IOException: Unable to locate binary
Title: Message Title James Howe commented on JENKINS-59584 Re: java.io.IOException: Unable to locate binary Downgrading back to 2.176.4 did not fix it. I'm not sure what to try now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202224.1569845119000.7800.1569846120125%40Atlassian.JIRA.
[JIRA] (JENKINS-59584) java.io.IOException: Unable to locate binary
Title: Message Title James Howe created an issue Jenkins / JENKINS-59584 java.io.IOException: Unable to locate binary Issue Type: Bug Assignee: Mads Mohr Christensen Components: adoptopenjdk-plugin Created: 2019-09-30 12:05 Environment: Jenkins 2.190.1 AdoptOpenJDK installer Plugin 1.2 Priority: Major Reporter: James Howe After upgrading Jenkins, the selected JDK is no longer being installed. I have tried jdk-11.0.4+11.4, jdk-11.0.4+11.4_openj9-0.15.1 and jdk-11.0.4+11.2. java.io.IOException: Unable to locate binary. ID: jdk-11.0.4+11.4_openj9-0.15.1, Platform: LINUX, CPU: amd64 at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:116) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) at hudson.model.JDK.forNode(JDK.java:147) at hudson.model.JDK.forNode(JDK.java:60) at org.jenkinsci.plugins.workflow.steps.ToolStep$Execution.run(ToolStep.java:152) at org.jenkinsci.plugins.workflow.steps.ToolStep$Execution.run(ToolStep.java:133) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at
[JIRA] (JENKINS-59051) Tool type "jgit" does not have an install of "jgit" configured
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-59051
Tool type "jgit" does not have an install of "jgit" configured
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-08-22 12:35
Environment:
Jenkins 2.176.2 Git Plugin 3.12.0
Labels:
pipeline
Priority:
Major
Reporter:
James Howe
The Declarative Directive Generator gives this for using a configured JGit tool
tools {
jgit 'jgit'
}
However, it doesn't actually work
Tool type "jgit" does not have an install of "jgit" configured - did you mean "null"?
The same happens for the Apache HTTP variant.
[JIRA] (JENKINS-58876) System.currentTimeSeconds not found in pipeline
Title: Message Title James Howe created an issue Jenkins / JENKINS-58876 System.currentTimeSeconds not found in pipeline Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-08-09 14:59 Environment: Jenkins 2.176.2 Script Security Plugin 1.62 Pipeline: Groovy 2.73 Labels: pipeline Priority: Minor Reporter: James Howe It works in the global script console but not in a (multi-branch) pipeline. No pending approval appears either. org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: No such static method found: staticMethod java.lang.System currentTimeSeconds at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:182) at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:189) at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:193) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:100) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript) at org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.withEnvBlock(ModelInterpreter.groovy:454) at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.callClosureForMapEntry(CpsDefaultGroovyMethods:5226) at com.cloudbees.groovy.cps.CpsDefaultGroovyMethods.collect(CpsDefaultGroovyMethods:3446) at
[JIRA] (JENKINS-58373) Restore "all" gates to version 5
Title: Message Title James Howe commented on JENKINS-58373 Re: Restore "all" gates to version 5 If the total of all issues >= threshold then make the build unstable. It was the same as putting the same number for each separate severity. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200494.1562587793000.8489.1562916660471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title James Howe edited a comment on JENKINS-58387 Re: Quality gates not working as expected Had a look at the code and realised the problem.It only evaluates the gates if the previous build exists, and had compatible dependency-check results.Instead it should always evaluate. If there are no results for the previous build results it should count that as zero issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200511.1562600834000.7899.1562842440121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title James Howe commented on JENKINS-58387 Re: Quality gates not working as expected Had a look at the code and realised the problem. It only evaluates the gates if the previous build exists, and had compatible dependency-check results. Instead it should always evaluate. If there are no results for the previous build it should count that as zero issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200511.1562600834000.7897.1562842380085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title James Howe commented on JENKINS-58387 Re: Quality gates not working as expected I cannot trivially reproduce it either using the same commit as before (config is also the same, being via Jenkinsfile). I have since upgraded to 5.0.1. The build that didn't become unstable simply logged [DependencyCheck] Collecting Dependency-Check artifact 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200511.1562600834000.7895.1562842260170%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title James Howe commented on JENKINS-58387 Re: Quality gates not working as expected It doesn't appear to have saved the source xml under the job result, but attached is the ResultAction. I'll sort out rebuilding that commit and dig it out. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200511.1562600834000.7893.1562841240134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title James Howe updated an issue Jenkins / JENKINS-58387 Quality gates not working as expected Change By: James Howe Attachment: resultaction.xml 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200511.1562600834000.7891.1562841180146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58375) Dependency check results rendering error
Title: Message Title James Howe commented on JENKINS-58375 Re: Dependency check results rendering error https://github.com/jeremylong/DependencyCheck/issues/2064 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200496.1562589011000.7887.1562840400119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58375) Dependency check results rendering error
Title: Message Title James Howe commented on JENKINS-58375 Re: Dependency check results rendering error I assume it's because it doesn't have a CWE. Other vulnerabilities are rendering correctly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200496.1562589011000.5469.1562668620045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58381) Restore trend graph
Title: Message Title James Howe commented on JENKINS-58381 Re: Restore trend graph I notice in the documentation that there is supposed to be, so I'm changing this to a bug. My jobs are multibranch declarative pipelines, if that's significant. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.5464.1562667600238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title James Howe updated an issue Jenkins / JENKINS-58381 Trend graph not appearing Change By: James Howe Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.5466.1562667600297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58381) Trend graph not appearing
Title: Message Title James Howe updated an issue Jenkins / JENKINS-58381 Trend graph not appearing Change By: James Howe Summary: Restore trend Trend graph not appearing 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200503.1562595115000.5465.1562667600284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58386) Add v4 xml parser
Title: Message Title James Howe commented on JENKINS-58386 Re: Add v4 xml parser As the previous version of the plugin appeared able to parse the v5 xml reports, this cannot be too much work. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200510.1562600049000.4690.1562601480081%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58386) Add v4 xml parser
Title: Message Title James Howe updated an issue Jenkins / JENKINS-58386 Add v4 xml parser Change By: James Howe Environment: dependency-check 5.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200510.1562600049000.4691.1562601480124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-58387
Quality gates not working as expected
Change By:
James Howe
{code:groovy}dependencyCheckPublisher unstableTotalCritical: 1, unstableTotalHigh: 1, unstableTotalMedium: 1, unstableTotalLow: 1{code}When there are no issues, the status is Success (/)When there is one medium issue, the status is Unstable (/)When there are two high and seven medium issues, the status is Success (x)
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200511.1562600834000.4684.1562601240134%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58386) Add v4 xml parser
Title: Message Title James Howe updated an issue Jenkins / JENKINS-58386 Add v4 xml parser Change By: James Howe To aid in migrations, especially when using native plugins to run the dependency check , and the increase in false-positives with v5 . Otherwise Perhaps more importantly, it's not possible to publish a report when building a previous version (and even worse, there's no error - JENKINS-58384).It's also odd that the plugin supports installing previous versions of the CLI, but is not able to use them. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200510.1562600049000.4683.1562601240105%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58387) Quality gates not working as expected
Title: Message Title James Howe created an issue Jenkins / JENKINS-58387 Quality gates not working as expected Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-08 15:47 Environment: dependency-check 5.0 Priority: Major Reporter: James Howe dependencyCheckPublisher unstableTotalCritical: 1, unstableTotalHigh: 1, unstableTotalMedium: 1, unstableTotalLow: 1 When there are no issues, the status is Success When there is one medium issue, the status is Unstable When there are two high and seven medium issues, the status is Success Add Comment
[JIRA] (JENKINS-58386) Add v4 xml parser
Title: Message Title James Howe created an issue Jenkins / JENKINS-58386 Add v4 xml parser Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-08 15:34 Priority: Minor Reporter: James Howe To aid in migrations, especially when using native plugins to run the dependency check. Otherwise it's not possible to publish a report when building a previous version (and even worse, there's no error - JENKINS-58384). It's also odd that the plugin supports installing previous versions of the CLI, but is not able to use them. Add Comment
[JIRA] (JENKINS-58384) Publisher should fail by default if no files found
Title: Message Title James Howe commented on JENKINS-58384 Re: Publisher should fail by default if no files found Parse errors don't cause failures either, only log messages: [DependencyCheck] Collecting Dependency-Check artifact [DependencyCheck] Unable to parse /var/lib/jenkins/node/workspace/a-platform_test-dependency-check/dependency-check-report.xml [DependencyCheck] Unsupported Dependency-Check schema version detected 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200508.1562597847000.4543.1562599680046%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58379) Snippet generator doesn't include file path
Title: Message Title James Howe updated an issue Jenkins / JENKINS-58379 Snippet generator doesn't include file path Change By: James Howe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200501.1562594446000.4485.1562598600155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58379) Snippet generator doesn't include file path
Title: Message Title
James Howe edited a comment on JENKINS-58379
Re: Snippet generator doesn't include file path
There is also no mention in [ the migration guide , [that the default |https://github.com/jenkinsci/dependency-check-plugin/wiki/v5-Migration] that the default is no longer {{**/dependency-check-report.xml}}.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200501.1562594446000.4470.1562598000623%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58384) Publisher should fail by default if no files found
Title: Message Title James Howe created an issue Jenkins / JENKINS-58384 Publisher should fail by default if no files found Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-08 14:57 Environment: dependency-check 5.0 Priority: Minor Reporter: James Howe Unlike similar plugins (and possibly previous versions of this), the publisher silently fails if no files are found. It should instead fail by default, with an option to ignore this error. Add Comment
[JIRA] (JENKINS-58379) Snippet generator doesn't include file path
Title: Message Title James Howe commented on JENKINS-58379 Re: Snippet generator doesn't include file path There is also no mention in the migration guide, that the default is no longer **/dependency-check-report.xml. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200501.1562594446000.4468.1562597760258%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58379) Snippet generator doesn't include file path
Title: Message Title James Howe commented on JENKINS-58379 Re: Snippet generator doesn't include file path Actually, the pattern argument doesn't do anything at all. I've submitted a PR for that, as it was a simple fix. The UI mapping looks more complicated, and I have no experience in that area. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200501.1562594446000.4463.1562597580153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55744) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe commented on JENKINS-55744 Re: Migrate from analysis-core to warnings-ng Any word on whether/when this might be done? My main interest at the moment is no longer needing to have the old plugins installed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197121.1548249042000.4380.1562596560513%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58373) Restore "all" gates to version 5
Title: Message Title James Howe commented on JENKINS-58373 Re: Restore "all" gates to version 5 See also the structure warnings-ng uses for recordIssues: qualityGates: [ [threshold: 1, type: 'TOTAL', unstable: true], [threshold: 5, type: 'TOTAL_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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200494.1562587793000.4314.1562595421412%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58381) Restore trend graph
Title: Message Title James Howe created an issue Jenkins / JENKINS-58381 Restore trend graph Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-08 14:11 Environment: dependency-check 5.0 Priority: Minor Reporter: James Howe With the removal of analysis-core (and not using its successor, warnings-ng) there is no longer a trend graph, nor any link on the job page to get to the latest results. Add Comment
[JIRA] (JENKINS-58379) Snippet generator doesn't include file path
Title: Message Title James Howe created an issue Jenkins / JENKINS-58379 Snippet generator doesn't include file path Issue Type: Bug Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-08 14:00 Environment: dependency-check 5.0 Jenkins 2.176.1 Priority: Minor Reporter: James Howe Even though the XML Report field appears, nothing is generated if a value is supplied. There is an argument called pattern, though the help doesn't mention that "XML Report" can be an ant pattern. Add Comment
[JIRA] (JENKINS-58375) Dependency check results rendering error
Title: Message Title James Howe created an issue Jenkins / JENKINS-58375 Dependency check results rendering error Issue Type: Bug Assignee: Unassigned Attachments: image-2019-07-08-13-29-14-101.png Components: dependency-check-jenkins-plugin Created: 2019-07-08 12:30 Environment: dependency-check 5.0 Jenkins 2.176.1 Priority: Minor Reporter: James Howe dependencycheck odcInstallation: 'v5' dependencyCheckPublisher() The resulting report has not replaced the $enc.xml($cweEntry) placeholder in the "Weakness" column.
[JIRA] (JENKINS-58373) Restore "all" gates to version 5
Title: Message Title James Howe created an issue Jenkins / JENKINS-58373 Restore "all" gates to version 5 Issue Type: Improvement Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-07-08 12:09 Priority: Major Reporter: James Howe The version 5 rewrite removed the unstableTotalAll and related options from dependencyCheckPublisher. This was a very convenient shortcut for unstableTotalCritical: x, unstableTotalHigh: x, unstableTotalMedium: x, unstableTotalLow: x. Can it be returned? Add Comment
[JIRA] (JENKINS-58345) Show trend graph on job summary, not full coverage results
Title: Message Title James Howe created an issue Jenkins / JENKINS-58345 Show trend graph on job summary, not full coverage results Issue Type: New Feature Assignee: Shenyu Zheng Components: code-coverage-api-plugin Created: 2019-07-04 13:59 Priority: Minor Reporter: James Howe To match most other plugins (warnings, test results, dependency-check, jacoco), the graph shown on the job summary should be the trend graph. Or, allow this to be configured. Add Comment This message was sent by
[JIRA] (JENKINS-28181) Incompatible with email-ext?
Title: Message Title James Howe updated an issue Jenkins / JENKINS-28181 Incompatible with email-ext? Change By: James Howe Component/s: email-ext-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162499.1430438854000.10507.1561630082527%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28181) Incompatible with email-ext?
Title: Message Title James Howe updated an issue Jenkins / JENKINS-28181 Incompatible with email-ext? Change By: James Howe Labels: email-ext nullpointer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162499.1430438854000.10511.1561630082962%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28181) Incompatible with email-ext?
Title: Message Title James Howe updated an issue Jenkins / JENKINS-28181 Incompatible with email-ext? Change By: James Howe Labels: 1.596.2 additional-identities-plugin email-ext nullpointer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162499.1430438854000.10500.1561630022635%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28181) Incompatible with email-ext?
Title: Message Title James Howe updated an issue Jenkins / JENKINS-28181 Incompatible with email-ext? Change By: James Howe Labels: 1.596.2 email-ext nullpointer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162499.1430438854000.10503.1561630022692%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58238) How to use with Bitbucket Cloud identities?
Title: Message Title James Howe created an issue Jenkins / JENKINS-58238 How to use with Bitbucket Cloud identities? Issue Type: Bug Assignee: Nicolas Bachschmidt Components: additional-identities-plugin Created: 2019-06-27 10:06 Priority: Minor Reporter: James Howe Now that Bitbucket Cloud doesn't have usernames, can this plugin still be used? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57887) Merge existing users
Title: Message Title James Howe created an issue Jenkins / JENKINS-57887 Merge existing users Issue Type: Improvement Assignee: Nicolas Bachschmidt Components: additional-identities-plugin Created: 2019-06-06 14:56 Priority: Minor Reporter: James Howe Multiple users for the same person have already been created (one login, one scm). Configuring additional identities for the login user to add the scm id doesn't appear to have any effect - both the separate users still appear on the People page. Are there additional steps that should be taken, or is this just not possible? Add Comment
[JIRA] (JENKINS-10258) Allow users unicity
Title: Message Title James Howe updated an issue Jenkins / JENKINS-10258 Allow users unicity Change By: James Howe Component/s: additional-identities-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140446.1310133744000.22726.1559831401080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52418) While adding new slave via Launch slave agent via ssh not able to select the via drop down existing credentials or new credentials which we have added recently
Title: Message Title James Howe commented on JENKINS-52418 Re: While adding new slave via Launch slave agent via ssh not able to select the via drop down existing credentials or new credentials which we have added recently I don't think this as anything to do with the Additional Identities plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192215.1530960754000.22719.1559831220150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56348) Add @Symbol("python") to ShiningPanda's PythonInstallation
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56348
Add @Symbol("python") to ShiningPanda's PythonInstallation
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no python. You have to use the full quoted class name instead.{code: java| title=Current}tools {'jenkins.plugins.shiningpanda.tools.PythonInstallation' 'CPython-3.6'}{code}{code: java| title=Proposed}tools {python : 'CPython-3.6'}{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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197934.1551459562000.21216.1559667060175%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56348) Add @Symbol("python") to ShiningPanda's PythonInstallation
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56348
Add @Symbol("python") to ShiningPanda's PythonInstallation
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no python. You have to use the full quoted class name instead.{code: groovy| title=Current}tools {'jenkins.plugins.shiningpanda.tools.PythonInstallation' : 'CPython-3.6'}{code}{code: groovy| title=Proposed}tools {python: 'CPython-3.6'}{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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197934.1551459562000.21215.155966757%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37388) Add @Symbol("ant") to Ant's ToolDescriptor
Title: Message Title
James Howe commented on JENKINS-37388
Re: Add @Symbol("ant") to Ant's ToolDescriptor
Andrew Bayer this one is resolved?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173485.1471099495000.5293.1558347960140%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37386) Add @Symbol to ToolDescriptors
Title: Message Title James Howe commented on JENKINS-37386 Re: Add @Symbol to ToolDescriptors Jesse Glick "jdk" and "maven" already work (or at least, they do now). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173483.1471099357000.5289.1558347840241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56348) Add @Symbol("python") to ShiningPanda's PythonInstallation
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56348
Add @Symbol("python") to ShiningPanda's PythonInstallation
Change By:
James Howe
Summary:
Add @Symbol( "python" alias for ) to ShiningPanda's PythonInstallation
Labels:
pipeline-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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197934.1551459562000.5285.1558347720058%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37390) Add @Symbol("docker") to Docker Common's ToolDescriptor
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-37390
Add @Symbol("docker") to Docker Common's ToolDescriptor
Change By:
James Howe
Labels:
newbie-friendly pipeline-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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173487.1471099627000.5251.1558346400417%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37390) Add @Symbol("docker") to Docker Common's ToolDescriptor
Title: Message Title
James Howe assigned an issue to Unassigned
Jenkins / JENKINS-37390
Add @Symbol("docker") to Docker Common's ToolDescriptor
Change By:
James Howe
Assignee:
Andrew Bayer
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173487.1471099627000.5254.1558346400455%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title James Howe edited a comment on JENKINS-56315 Re: Add "docker" alias for DockerTool Seems there's already a PR for this, but it was closed without explanation further development . 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197895.1551292982000.5256.1558346401159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title James Howe closed an issue as Duplicate Seems there's already a PR for this, but it was closed without explanation. Jenkins / JENKINS-56315 Add "docker" alias for DockerTool Change By: James Howe Status: Open Closed Resolution: Duplicate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197895.1551292982000.5248.1558346220324%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe updated an issue Jenkins / JENKINS-55597 Jenkins JNLP agent disconnects when it fails to delete an old build workspace Change By: James Howe Component/s: remoting Component/s: ssh-agent-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.609.1557852840261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe updated an issue Jenkins / JENKINS-55597 Jenkins JNLP agent disconnects when it fails to delete an old build workspace Change By: James Howe Component/s: ssh-agent-plugin Component/s: ws-cleanup-plugin Component/s: _unsorted 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.601.1557852780362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe commented on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace To justify a security patch, any user who can submit a job the uses Docker can probably use this to make a DoS attack. That's how I'm getting it - the docker container runs as root and can write to the workspace, resulting in files the jenkins user cannot delete. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.579.1557851940436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe edited a comment on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace To justify a security patch, any user who can submit a job the that uses Docker can probably use this to make a DoS attack.That's how I'm getting it - the docker container runs as root and can write to the workspace, resulting in files the jenkins user cannot delete. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.581.1557851940472%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55597) Jenkins JNLP agent disconnects when it fails to delete an old build workspace
Title: Message Title James Howe commented on JENKINS-55597 Re: Jenkins JNLP agent disconnects when it fails to delete an old build workspace This also appears to affect SSH agents in 2.164.3, although the exception is a channel EOF instead of the FileSystemException. Deleting the directory manually allows the agent to startup correctly. Can this fix be ported to LTS please? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196765.1547550769000.33.1557827400268%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55745) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe commented on JENKINS-55745 Re: Migrate from analysis-core to warnings-ng Perhaps you should've linked the conversation here before deciding there weren't enough replies. As far as I can see, of the two responses, one wanted A1 (just the warnings-ng parser) and the other wanted B. I'm in the former camp, and just need the reporting capability, and would favour all reporting being integrated. If there's a parser for warnings-ng, then I probably have no need for a separate dependency-check plugin. Is it possible you could provide the parser for warnings-ng as well as your planned implementation of option B? I'm guessing, given your experience, you'd have the least trouble producing it quickly. 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-56466) Bitbucket key is unmasked in logs
Title: Message Title James Howe updated an issue Jenkins / JENKINS-56466 Bitbucket key is unmasked in logs Change By: James Howe 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-56526) Cannot get excludeMessage to work
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-56526
Cannot get excludeMessage to work
Issue Type:
Bug
Assignee:
Ulli Hafner
Attachments:
image-2019-03-12-15-23-52-019.png
Components:
warnings-ng-plugin
Created:
2019-03-12 15:25
Environment:
Jenkins 2.150.3 Warnings Next Generation Plugin 3.0.3
Priority:
Major
Reporter:
James Howe
Step
recordIssues tool: mavenConsole(),
filters: [excludeType('maven-surefire-plugin:test'),
excludeMessage('.*A new version of dependency-check is available.*')],
qualityGates: [[threshold: 1, type: 'TOTAL', unstable: true]]
Console (643-649)
[INFO] --- dependency-check-maven:4.0.2:check (default) @ logger-tcp-server ---
[JIRA] (JENKINS-56466) Bitbucket key is unmasked in logs
Title: Message Title James Howe created an issue Jenkins / JENKINS-56466 Bitbucket key is unmasked in logs Issue Type: Bug Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2019-03-07 15:39 Environment: Jenkins 2.150.3 Bitbucket Build Status Notifier Plugin 1.4.1 Labels: security Priority: Minor Reporter: James Howe The plugin logs the secret key in plaintext at INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusHelper sendBuildStatusNotification in both the "This request was sent" and "This response was received" messages. Add Comment
[JIRA] (JENKINS-56465) Job-based API Tokens
Title: Message Title James Howe created an issue Jenkins / JENKINS-56465 Job-based API Tokens Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-03-07 15:29 Priority: Minor Reporter: James Howe It would be very useful to be able to configure API tokens (and their access rights) for a job (including Folders). It's a common situation where your security realm (LDAP, AD, etc.) is not managed by the same people who manage Jenkins. Therefore "service" users cannot be created in order to e.g. grant read access to job status/artifacts. It's also not possible to generate tokens for yourself that grant less access that you have. Add Comment
[JIRA] (JENKINS-56463) API token matched for user foo but the impersonation failed
Title: Message Title James Howe created an issue Jenkins / JENKINS-56463 API token matched for user foo but the impersonation failed Issue Type: Bug Assignee: Unassigned Components: core, ldap-plugin Created: 2019-03-07 15:13 Environment: Jenkins 2.150.3 LDAP Plugin 1.20 Priority: Minor Reporter: James Howe Attempting to use an API token for a user that exists in Jenkins but isn't in the current Security Realm returns a 500, with this in the logs. Mar 07, 2019 3:07:24 PM WARNING jenkins.security.BasicHeaderApiTokenAuthenticator authenticate API token matched for user foo but the impersonation failed org.acegisecurity.userdetails.UsernameNotFoundException: User foo not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1314) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1251) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.getUserDetailsForImpersonation(User.java:398) at jenkins.security.BasicHeaderApiTokenAuthenticator.authenticate(BasicHeaderApiTokenAuthenticator.java:35) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] (JENKINS-56348) Add "python" alias for PythonInstallation
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-56348
Add "python" alias for PythonInstallation
Issue Type:
Improvement
Assignee:
Unassigned
Components:
shiningpanda-plugin
Created:
2019-03-01 16:59
Priority:
Minor
Reporter:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no python. You have to use the full quoted class name instead.
Current
tools {
'jenkins.plugins.shiningpanda.tools.PythonInstallation': 'CPython-3.6'
}
Proposed
tools {
python: 'CPython-3.6'
}
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title James Howe commented on JENKINS-56315 Re: Add "docker" alias for DockerTool Hopefully it doesn't collide with pipeline.agent.docker or the global docker (which also provides docker.withTool()). 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-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy}tools {docker: 'latest'}{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-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy|title=Current} tools { 'org.jenkinsci.plugins.docker.commons.tools.DockerTool': 'latest'}{ code }{code :groovy |title=Proposed }tools {docker: 'latest'}{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-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy|title=Current} tools { 'org.jenkinsci.plugins.docker.commons.tools.DockerTool': 'latest'}{ code }{code :groovy |title=Proposed }tools {docker: 'latest'}{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-56315) Add "docker" alias for DockerTool
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56315
Add "docker" alias for DockerTool
Change By:
James Howe
Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. {code:groovy}tools {docker: 'latest'}{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-56346) Provide build wrapper withDockerCompose
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56346
Provide build wrapper withDockerCompose
Change By:
James Howe
Currently I've built my own in a custom library{code :groovy }def call(Closure body) {docker.withTool('Default') {withPythonEnv('python') {sh 'pip install docker-compose'sh 'docker-compose --no-ansi up -d'try {waitUntil { script { dockerUtils.isReady() } }body()} finally {sh 'docker-compose --no-ansi down'}}}}{code}The {{isReady()}} function is a little complicated - it essentially does{code :sh }docker inspect --format '{{json .State}}' $(docker-compose ps -q){code}then parses and checks that every container has either {{Health.Status == 'healthy'}}, or {{Status == 'running'}} if there is no healthcheck.You could implement something similar, and more configurable, directly.
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-56346) Provide build wrapper withDockerCompose
Title: Message Title
James Howe updated an issue
Jenkins / JENKINS-56346
Provide build wrapper withDockerCompose
Change By:
James Howe
Currently I've built my own in a custom library{code :groovy }def call(Closure body) { docker.withTool('Default') { withPythonEnv('python') {sh 'pip install docker-compose'sh 'docker-compose --no-ansi up -d'try {waitUntil { script { dockerUtils.isReady() } }body()} finally {sh 'docker-compose --no-ansi down'}}} } {code}The {{isReady()}} function is a little complicated - it essentially does{code :sh }docker inspect --format '{{json .State}}' $(docker-compose ps -q){code} then parses and checks that every container has either {{Health.Status == 'healthy'}}, or {{Status == 'running'}} if there is no healthcheck.You could implement something similar, and more configurable, directly.
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-56346) Provide build wrapper withDockerCompose
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-56346
Provide build wrapper withDockerCompose
Issue Type:
Improvement
Assignee:
João Galego
Components:
docker-compose-build-step-plugin
Created:
2019-03-01 16:42
Priority:
Minor
Reporter:
James Howe
Currently I've built my own in a custom library
def call(Closure body) {
withPythonEnv('python') {
sh 'pip install docker-compose'
sh 'docker-compose --no-ansi up -d'
try {
waitUntil { script { dockerUtils.isReady() } }
body()
} finally {
sh 'docker-compose --no-ansi down'
}
}
}
The isReady() function is a little complicated - it essentially does
docker inspect --format '{{json .State}}' $(docker-compose ps -q)
then parses and checks that every container has either Health.Status == 'healthy', or Status == 'running' if there is no healthcheck. You could implement something similar, and more configurable, directly.
[JIRA] (JENKINS-56345) Manage tool installation for docker compose
Title: Message Title James Howe created an issue Jenkins / JENKINS-56345 Manage tool installation for docker compose Issue Type: Improvement Assignee: João Galego Components: docker-compose-build-step-plugin Created: 2019-03-01 16:32 Priority: Minor Reporter: James Howe I guess with one of the installation options be to grab the release from github. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56344) Docker compose aliases for declarative pipeline
Title: Message Title James Howe created an issue Jenkins / JENKINS-56344 Docker compose aliases for declarative pipeline Issue Type: Improvement Assignee: João Galego Components: docker-compose-build-step-plugin Created: 2019-03-01 16:30 Priority: Minor Reporter: James Howe Currently the simplest snippet you can use is this step([$class: 'DockerComposeBuilder', dockerComposeFile: 'docker-compose.yml', option: [$class: 'StartAllServices'], useCustomDockerComposeFile: false]) it would be much nicer to have aliases for the classes and defaults for the arguments dockerCompose 'startAllServices' or one for each option dockerComposeUp() dockerComposeDown 'db'
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title James Howe commented on JENKINS-56330 Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2 If the code is moved to a global shared library, thus bypassing the sandbox, everything works fine. 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-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title
James Howe edited a comment on JENKINS-56330
Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Probably related, but it's also not possible to use ` {{ CurriedClosure ` }} with Java 8 streams, even though it should be a ` {{ @FunctionalInterface ` }} via ` {{ Runnable ` }} .{noformat}hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.util.stream.ReferencePipeline$Head.map() is applicable for argument types: (org.codehaus.groovy.runtime.CurriedClosure) values: [org.codehaus.groovy.runtime.CurriedClosure@6846ac99]Possible solutions: map(java.util.function.Function), max(java.util.Comparator), min(java.util.Comparator), wait(), any(), dump() at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153) {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title James Howe commented on JENKINS-56330 Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2 Probably related, but it's also not possible to use `CurriedClosure` with Java 8 streams, even though it should be a `@FunctionalInterface` via `Runnable`. hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.util.stream.ReferencePipeline$Head.map() is applicable for argument types: (org.codehaus.groovy.runtime.CurriedClosure) values: [org.codehaus.groovy.runtime.CurriedClosure@6846ac99] Possible solutions: map(java.util.function.Function), max(java.util.Comparator), min(java.util.Comparator), wait(), any(), dump() at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153) 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-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title
James Howe edited a comment on JENKINS-56330
Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Same exception with this arrangement too {code: groovy| title=Jenkinsfile}pipeline { stages {stage('Build') { script {env. PGPORT PORT = new ServerSocket(0).withCloseable { s -> s.getLocalPort() } } // ...{code}{noformat:title=Stacktrace}hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.net.ServerSocket.withCloseable() is applicable for argument types: (org.jenkinsci.plugins.workflow.cps.CpsClosure2) values: [org.jenkinsci.plugins.workflow.cps.CpsClosure2@2e112848]Possible solutions: withCloseable(groovy.lang.Closure), withCloseable(groovy.lang.Closure) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:22) at ___cps.transform___(Native Method) [ same as above ]{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title James Howe updated an issue Jenkins / JENKINS-56330 Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2 Change By: James Howe Environment: Jenkins 2.150.3Pipeline 2.6Pipeline: Declarative 1.3.4.1Pipeline: Groovy 2.63 Script Security 1.53 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-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title James Howe updated an issue Jenkins / JENKINS-56330 Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2 Change By: James Howe Component/s: script-security-plugin Component/s: workflow-cps-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title
James Howe commented on JENKINS-56330
Re: Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Same exception with this arrangement too
Jenkinsfile
pipeline {
stages {
stage('Build') {
script {
env.PGPORT = new ServerSocket(0).withCloseable { s -> s.getLocalPort() }
}
// ...
Stacktrace
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.net.ServerSocket.withCloseable() is applicable for argument types: (org.jenkinsci.plugins.workflow.cps.CpsClosure2) values: [org.jenkinsci.plugins.workflow.cps.CpsClosure2@2e112848]
Possible solutions: withCloseable(groovy.lang.Closure), withCloseable(groovy.lang.Closure)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:153)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:22)
at ___cps.transform___(Native Method)
[ same as above ]
Add Comment
This
[JIRA] (JENKINS-31449) Port Allocator Pipeline support
Title: Message Title James Howe commented on JENKINS-31449 Re: Port Allocator Pipeline support Oliver Gondža Richard Mortimer Are either of you able to sort this out? I'm not sure if the PR needs updating e.g. for declarative support. 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-56330) Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Title: Message Title
James Howe created an issue
Jenkins / JENKINS-56330
Expecting groovy.lang.Closure, got org.jenkinsci.plugins.workflow.cps.CpsClosure2
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-02-28 15:20
Environment:
Jenkins 2.150.3 Pipeline 2.6 Pipeline: Declarative 1.3.4.1 Pipeline: Groovy 2.63
Priority:
Major
Reporter:
James Howe
Jenkinsfile
static def freePort() {
return new ServerSocket(0).withCloseable { s -> s.getLocalPort() }
}
pipeline {
stages {
stage('Build') {
environment {
PORT = freePort()
}
// ...
Stacktrace
hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: java.net.ServerSocket.withCloseable() is applicable for argument types: (org.jenkinsci.plugins.workflow.cps.CpsClosure2) values: [org.jenkinsci.plugins.workflow.cps.CpsClosure2@1869b1e7]
Possible solutions:
[JIRA] (JENKINS-56315) Add "docker" alias for DockerTool
Title: Message Title James Howe created an issue Jenkins / JENKINS-56315 Add "docker" alias for DockerTool Issue Type: Improvement Assignee: Unassigned Components: docker-commons-plugin Created: 2019-02-27 18:43 Labels: pipeline-improvement Priority: Minor Reporter: James Howe Most other tool implementations provide a short name for use in pipelines (jdk, maven, etc.) but there's no docker. You have to use the full quoted class name instead. Add Comment
[JIRA] (JENKINS-53445) NPE and JVM Version not shown for Java 11
Title: Message Title James Howe commented on JENKINS-53445 Re: NPE and JVM Version not shown for Java 11 Adrien Lecharpentier that's fine, as everything else seemed to work. Another thing to be aware of is confused Ubuntu users: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1796027 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-19947) Missing base directory in ZIP from .../artifact/dir/subdir/*zip*/subdir.zip
Title: Message Title James Howe commented on JENKINS-19947 Re: Missing base directory in ZIP from .../artifact/dir/subdir/*zip*/subdir.zip I don't suppose there's any option if I want the directory to be omitted? 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-55745) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe created an issue Jenkins / JENKINS-55745 Migrate from analysis-core to warnings-ng Issue Type: Task Assignee: Unassigned Components: dependency-check-jenkins-plugin Created: 2019-01-23 13:15 Priority: Minor Reporter: James Howe This plugin currently depends on Static Analysis Utilities, which is EOL and replaced by Warnings Next Generation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55744) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe created an issue Jenkins / JENKINS-55744 Migrate from analysis-core to warnings-ng Issue Type: Task Assignee: David van Laatum Components: email-ext-plugin Created: 2019-01-23 13:10 Priority: Minor Reporter: James Howe This plugin currently depends on Static Analysis Utilities, which is EOL and replaced by Warnings Next Generation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-40127) Declarative Pipeline GDSL
Title: Message Title James Howe commented on JENKINS-40127 Re: Declarative Pipeline GDSL Gonzalo Garcia if you have code that generates the GSDL please share it. The result will be different for every Jenkins instance depending on what plugins (and versions thereof) are installed. 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-41813) bitbucket branch source folder no longer can have views
Title: Message Title James Howe commented on JENKINS-41813 Re: bitbucket branch source folder no longer can have views There's no way to customise the columns in the folders then? You have to recreate the whole structure manually with views instead? 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-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title James Howe commented on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace Just to note: I performed a System.gc() to force a full garbage collection If you have -XX:+ExplicitGCInvokesConcurrent then it doesn't do a "full" collection. 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title James Howe commented on JENKINS-48463 Re: Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Just to add, as far as I can tell you only need 1.1 if you've got control characters in names (i.e. of tags and attributes). Surely if people are putting them in their configuration it's in text content, where 1.0 works just fine. Not only does .NET not support xml 1.1 but neither does Firefox, nor any of my editors. 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.
