[JIRA] (JENKINS-57207) Azure VM agents still provision when Jenkins is "preparing for shutdown"
Title: Message Title R. Tyler Croy commented on JENKINS-57207 Re: Azure VM agents still provision when Jenkins is "preparing for shutdown" I'm not entirely sure what good reproduction case would be, since I encountered this issue when: An Azure server side error (maximum deployments for quota) caused provisioning of agents to fail. I put Jenkins in "Prepare for Shutdown" mode I deleted deployments in Azure, allowing new deployments to be created. It might be reproducible if you disconnected a master from the network, so that it couldn't reach an Azure API. Then triggered a pipeline which would cause a VM to provision. Then once the plugin starts to try to provision, put the master in shutdown mode, and reconnect the network. Just a thought, but definitely a tricky failure to reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57207) Azure VM agents still provision when Jenkins is "preparing for shutdown"
Title: Message Title Jie Shen commented on JENKINS-57207 Re: Azure VM agents still provision when Jenkins is "preparing for shutdown" How can I reproduce this issue or how to detect the "preparing to shutdown" status of the master? 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-57204) Provision failures does not clean up deployments
Title: Message Title Jie Shen commented on JENKINS-57204 Re: Provision failures does not clean up deployments Thanks for reporting this issue. It is similar as JENKINS-48045 in VM agent plugin. I will make a PR soon to fix this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57203) OWASP Dependency-Check Plugin is unable to read results from the Node Security Project (NspAnalyzer)
Title: Message Title Steve Springett closed an issue as Not A Defect NSP was removed from Dependency-Check in v3.3.4 - current version is 4.0.2. Also, I do not open random word documents. Upgrade to 4.0.2 and the issue should disappear. Additionally, the functionality reported is not specific to the Jenkins plugin, rather, part of Dependency-Check itself (Jenkins simply wraps it). If you continue to experience this issue, you'll need to open an issue on the Dependency-Check project. Jenkins / JENKINS-57203 OWASP Dependency-Check Plugin is unable to read results from the Node Security Project (NspAnalyzer) Change By: Steve Springett Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-57207) Azure VM agents still provision when Jenkins is "preparing for shutdown"
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-57207 Azure VM agents still provision when Jenkins is "preparing for shutdown" Change By: Jie Shen Assignee: Azure DevOps Jie Shen 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-57204) Provision failures does not clean up deployments
Title: Message Title Azure DevOps started work on JENKINS-57204 Change By: Azure DevOps Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57143) JNLP4 error: "Connection closed before acknowledgement sent"
Title: Message Title Alexey Shein commented on JENKINS-57143 Re: JNLP4 error: "Connection closed before acknowledgement sent" I suggest double-checking your configuration. Make sure the version 4 protocol is allowed. Take a look at any other settings that might be relevant. It is enabled. I've enabled also JNLP 3 and it is used now as a fallback when JNLP4 connect fails. Which agent version do you have? INFO: Using Remoting version: 3.29 Any idea how to debug that? I tried to use loggingConfig option, but couldn't make it work (also not sure what to write in the file). Maybe some plugins that can affect that? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57194) Jenkins not deactivating nodes below the free space threshold
Title: Message Title Daniel Beck closed an issue as Not A Defect Works as intended, node monitors update hourly: https://github.com/jenkinsci/jenkins/blob/811583eb6007ffa22f81c312d983816e5f36a670/core/src/main/java/hudson/node_monitors/AbstractNodeMonitorDescriptor.java#L325 Jenkins / JENKINS-57194 Jenkins not deactivating nodes below the free space threshold Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect 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-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Gavin Mogan commented on JENKINS-57200 Re: Can't access builds in BlueOcean after updating to 1.15.0 oh shoot this was me. Looks like its here https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-rest-impl/src/main/java/io/jenkins/blueocean/service/embedded/rest/ChangeSetContainerImpl.java#L54-L61 Re-reading it again, it looks like it'll loop infinitely if the job its replaying has been deleted already. I'll add an exit clause 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-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-57200 Can't access builds in BlueOcean after updating to 1.15.0 Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57207) Azure VM agents still provision when Jenkins is "preparing for shutdown"
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-57207 Azure VM agents still provision when Jenkins is "preparing for shutdown" Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-04-27 15:52 Priority: Minor Reporter: R. Tyler Croy With the latest version of Jenkins and the plugin on ci.jenkins.io, I noticed today that even when the master is "preparing to shutdown" (i.e. the queue is in read-only mode, etc), the Azure VM Agents plugin continues to provision Azure agents. I would expect that "preparing for shutdown" would cause the agents not to provision Add Comment
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title
Mark Waite edited a comment on JENKINS-51638
Re: No Enum Constant Found - Default PreBuildMerge Failure
The fix that [~jglick] has provided is working well in my testing of git plugin 4.0 pre-release. I can see the failure with git plugin 3.9.4 and can confirm that it is resolved in the 4.0 pre-release. I haven't yet tested it with the git plugin 3.10 pre-release, but I expect no issue in that pre-release version either.While testing the fix that [~jglick] has provided for git plugin 4.0 and git plugin 3.10, I found a null pointer exception that I need to investigate further when using JGit as the git implementation. The stack trace was:{noformat}java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getRevisionForSHA1(GitUtils.java:166) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:119) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1058) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1151) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834){noformat}I'll refer to [my jenkins-bugs test repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-51638] for the details. Problem logged as JENKINS-57205
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title
asgeirn created an issue
Jenkins / JENKINS-57206
Support draft pull requests from GitHub
Issue Type:
Improvement
Assignee:
Unassigned
Components:
github-branch-source-plugin
Created:
2019-04-27 15:36
Environment:
OpenJDK 1.8.0_212-8u212-b01-1~deb9u1-b01, Jenkins 2,164.2, github-branch-source 2.4.5 os.arch amd64 os.name Linux os.version 4.15.0-1037-azure
Priority:
Minor
Reporter:
asgeirn
We use GitHub PRs as conditions to build prerelease version of our applications using the following pipeline clause: {{ when { changeRequest() }}} However, if we create the pull requests as draft pull requests (a nice feature for in-progress work), Jenkins does not detect the PR or create any build for it. We have enabled the traits below, but I cannot find any hints regarding draft PRs: {{ }} {{ branch_source.BranchDiscoveryTrait>}} {{ 1}} {{ branch_source.BranchDiscoveryTrait>}} {{ branch_source.OriginPullRequestDiscoveryTrait>}} {{ 1}} {{ branch_source.OriginPullRequestDiscoveryTrait>}} {{ branch_source.ForkPullRequestDiscoveryTrait>}} {{ 1}} {{ }} {{ branch_source.ForkPullRequestDiscoveryTrait>}} {{ branch_source.TagDiscoveryTrait/>}} {{ }}
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57205
Null pointer exception in JGit pre-build merge
Change By:
Mark Waite
While testing the fix that [~jglick] has provided for JENKINS-51638 in git plugin 4.0 and git plugin 3.10, I found a null pointer exceptionwhen using JGit as the git implementation. The stack trace was:{noformat}java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getRevisionForSHA1(GitUtils.java:166) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:119) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1058) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1151) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834){noformat}Refer to [my jenkins-bugs test repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-51638] for the details. The failure seemed to be intermittent and limited to the JGit implementation. It was not visible in the command line git implementation.
Add Comment
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57205
Null pointer exception in JGit pre-build merge
Change By:
Mark Waite
While testing the fix that [~jglick] has provided for JENKINS-51638 in git plugin 4.0 and git plugin 3.10, I found a null pointer exception that I need to investigate further when exceptionwhen using JGit as the git implementation. The stack trace was:{noformat}java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getRevisionForSHA1(GitUtils.java:166) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:119) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1058) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1151) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834){noformat} I'll refer Refer to [my jenkins-bugs test repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-51638] for the details.
Add Comment
[JIRA] (JENKINS-57204) Provision failures does not clean up deployments
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-57204
Provision failures does not clean up deployments
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-container-agents-plugin
Created:
2019-04-27 15:26
Priority:
Critical
Reporter:
R. Tyler Croy
We're seeing a number of failures on ci.jenkins.io which stem from Azure Container Agents failing to provision. It looks like failed ACI deployments don't get cleaned up automatically by the plugin. ACI is returning the following failure:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"error\": {\r\n \"code\": \"ServiceUnavailable\",\r\n \"message\": \"The requested resource is not available in the location 'eastus2' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '4' GB memory 'Linux' OS\"\r\n }\r\n}"}]}
Which is annoying, but whatever. The bug here is that the plugin does not clean up this failed deployment, so we have exceeded our quota of Deployments of 800, all failures like this one! I recall this exact same issue in the Azure VM Agents plugin at one point as well.
[JIRA] (JENKINS-57205) Null pointer exception in JGit pre-build merge
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-57205 Null pointer exception in JGit pre-build merge Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-04-27 15:26 Priority: Minor Reporter: Mark Waite While testing the fix that Jesse Glick has provided for git plugin 4.0 and git plugin 3.10, I found a null pointer exception that I need to investigate further when using JGit as the git implementation. The stack trace was: java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getRevisionForSHA1(GitUtils.java:166) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:119) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1058) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1151) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) I'll refer to my jenkins-bugs test repository for the details.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Mark Waite commented on JENKINS-51638 Re: No Enum Constant Found - Default PreBuildMerge Failure Interactive tests passed with the git plugin 3.10 pre-release as well. 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-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Mark Waite commented on JENKINS-51638 Re: No Enum Constant Found - Default PreBuildMerge Failure The fix that Jesse Glick has provided is working well in my testing of git plugin 4.0 pre-release. I can see the failure with git plugin 3.9.4 and can confirm that it is resolved in the 4.0 pre-release. I haven't yet tested it with the git plugin 3.10 pre-release, but I expect no issue in that pre-release version either. While testing the fix that Jesse Glick has provided for git plugin 4.0 and git plugin 3.10, I found a null pointer exception that I need to investigate further when using JGit as the git implementation. The stack trace was: java.lang.NullPointerException at hudson.plugins.git.util.GitUtils.getRevisionForSHA1(GitUtils.java:166) at hudson.plugins.git.extensions.impl.PreBuildMerge.decorateRevisionToBuild(PreBuildMerge.java:119) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:1058) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1151) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834) I'll refer to my jenkins-bugs test repository for the details. Add Comment This
[JIRA] (JENKINS-47271) Cloud Foundry Plugin fails when using inherit in manifest
Title: Message Title Leela Sankar Pinjala commented on JENKINS-47271 Re: Cloud Foundry Plugin fails when using inherit in manifest Hi Steven, Is this fix released? 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-48715) Retain last N builds
Title: Message Title Martin d'Anjou updated an issue Jenkins / JENKINS-48715 Retain last N builds Change By: Martin d'Anjou Labels: newbie-friendly 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-34641) Update CCtray (cc.xml) to support Jenkins2 folders
Title: Message Title Daniel Beck closed an issue as Fixed https://github.com/jenkinsci/jenkins/pull/3060 and https://github.com/jenkinsci/jenkins/pull/3081 made it into core, and the first actual release of cctray-xml plugin includes those changes (in a slightly different form) Docs: https://github.com/jenkinsci/cctray-xml-plugin#usage Jenkins / JENKINS-34641 Update CCtray (cc.xml) to support Jenkins2 folders Change By: Daniel Beck Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56785) default git checkout is not working while creating pipeline jobs
Title: Message Title Mohit Saraf commented on JENKINS-56785 Re: default git checkout is not working while creating pipeline jobs Thank you for your reponse. Installing git in master node solved the problem. 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-57203) OWASP Dependency-Check Plugin is unable to read results from the Node Security Project (NspAnalyzer)
Title: Message Title Anuj Gupta created an issue Jenkins / JENKINS-57203 OWASP Dependency-Check Plugin is unable to read results from the Node Security Project (NspAnalyzer) Issue Type: Bug Assignee: Unassigned Attachments: OWASP Dependency Check.docx Components: dependency-check-jenkins-plugin Created: 2019-04-27 08:30 Priority: Blocker Reporter: Anuj Gupta Hello, I have configured OWASP Dependency Check Plugin for security scan but I am getting following error in console output : [DependencyCheck] Scanning: /var/lib/jenkins/workspace/XXX [DependencyCheck] Analyzing Dependencies [DependencyCheck] One or more exceptions were thrown while executing Dependency-Check [DependencyCheck] Exception Caught: org.owasp.dependencycheck.analyzer.exception.AnalysisException [DependencyCheck] Cause: api.nodesecurity.io [DependencyCheck] Message: Failed to read results from the Node Security Project (NspAnalyzer); the analyzer is being disabled and may result in false negatives. [DependencyCheck] org.owasp.dependencycheck.analyzer.exception.AnalysisException: Failed to read results from the Node Security Project (NspAnalyzer); the analyzer is being disabled and may result in false negatives. [DependencyCheck] at org.owasp.dependencycheck.analyzer.NspAnalyzer.analyzeDependency(NspAnalyzer.java:222) [DependencyCheck] at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze(AbstractAnalyzer.java:136) [DependencyCheck] at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:88) [DependencyCheck] at org.owasp.dependencycheck.AnalysisTask.call(AnalysisTask.java:37) [DependencyCheck] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [DependencyCheck] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [DependencyCheck]
[JIRA] (JENKINS-57202) p4 workspace -o "No output for" after upgrade mac slave to 10.13
Title: Message Title bav ver created an issue Jenkins / JENKINS-57202 p4 workspace -o "No output for" after upgrade mac slave to 10.13 Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-04-27 07:18 Environment: windows master / MacOS slave - latest Jenkins version Priority: Blocker Reporter: bav ver My windows/mac jobs ran fine. For building some Botan lib on macOS slave, i had to upgrade Xcode, then macOS from macOS 10.10 to 10.13. Afterwards, i noticed that the jenkins job build fails with the error 'no output for p4'. In pre-build i execute p4 commands ok (correct output), but all of a sudden Jenkins then performs p4 workspace -o and this fails with error Caught exception communicating with perforce. No output for: p4 workspace -o ... That command runs fine when run from terminal command window on mac slave; apparently not within Jenkins job. Add Comment
