[JIRA] (JENKINS-54076) Polling keeps building without changes on error

2018-10-15 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54076  
 
 
  Polling keeps building without changes on error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-10-15 06:31  
 
 
Environment: 
 Jenkins 2.121.2, P4 1.8.15  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Wouter Slob  
 

  
 
 
 
 

 
 We've got a pipeline containing a shared library and multiple p4 checkout steps on different servers, with different p4 clients. Polling perforce detects changes and starts build. But if the build fails, the next polling step again changes are found, event though there are none and a new build is started, over and over again. The Polling Log shows:   

 

This page captures the polling log that triggered this build.Started on XXX
no polling baseline in D:\Jenkins\workspace\XXX@libs\shared-library on 
P4: Polling on: master with:XXX_Build
Found last change 1129035 on syncID XXX_Build
... p4 client -o XXX_Build
 +... p4 info
 +
P4 Task: establishing connection.
... server: perforce:1666
... node: XXX
P4: Polling with range: 1129035,now
... p4 changes -m20 //XXX_Build/...@1129035,now
 +P4: Polling on: master with:XXX_Package
Done. Took 0.56 sec
Changes found
 

 1129035 was the last change for our view and there are no new changes after this change. Any help on how to stop the Polling from thinking there are changes?      

[JIRA] (JENKINS-54075) Polling Log Javascript Error: "toggle is not defined"

2018-10-15 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54075  
 
 
  Polling Log _javascript_ Error: "toggle is not defined"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 p4-plugin  
 
 
Created: 
 2018-10-15 06:20  
 
 
Environment: 
 Jenkins 2.138.1, p4 1.9.1, Edge, Chrome  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Wouter Slob  
 

  
 
 
 
 

 
 The "Perforce Software Polling Log" contains several "+" hyperlinks, eg after the "p4 client" or "p4 info" actions. When clicking on the "+" nothing happens. The browser console shows an error message: "Uncaught ReferenceError: toggle is not defined"  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-50456) Pipeline continues after powershell error

2018-03-28 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Confirmed! This works: node("") {     ws("x:\src") {         powershell 'Copy-Item "a.xml" -Destination "b.xml" -ErrorAction Stop'     } }   Thnx!  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50456  
 
 
  Pipeline continues after powershell error   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you 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-50456) Pipeline continues after powershell error

2018-03-28 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob commented on  JENKINS-50456  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline continues after powershell error   
 

  
 
 
 
 

 
 Sam Van Oort: can you please have a look? Thnx!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-50456) Pipeline continues after powershell error

2018-03-28 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50456  
 
 
  Pipeline continues after powershell error   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 

  
 
 
 
 

 
 Pipeline script continues after errors in powershell script. * Pipeline (none of the mentioned files exist!): *  node _node ("...") \{ _       ws  _ws ("x:\src") \{ _           powershell  _powershell  'Copy-Item "a.xml" -Destination "b.xml"' _       _  } _   _  } _  * output: *   _  [Pipeline] \{ _   _  [Pipeline]  ws  ws_   Running  _Running  in x:\ src src_   _  [Pipeline] \{ _   _  [Pipeline]  powershell  powershell_   _  [src] Running PowerShell  script  script_   powershell  _powershell .exe : Copy-Item : Cannot find path 'X:\src\a.xml' because it does not exist. _   At  _At  X:\src@tmp\durable-472cdca6\powershellWrapper.ps1:5 char: 3 3_   _  + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Fi ... _   _  + ~~~ _   _  + CategoryInfo : NotSpecified: (Copy-Item : Can...does not exist. :String) [],  RemoteException  RemoteException_   _  + FullyQualifiedErrorId :  NativeCommandError  NativeCommandError_  At _At  X:\src@tmp\durable-472cdca6\powershellScript.ps1:1 char: 1 1_  _ + Copy-Item "a.xml" -Destination "b.xml" _  _ + ~~ _  _ + CategoryInfo : ObjectNotFound: (X:\src\a.xml:String) [Copy- Item Item_  _ ],  ItemNotFoundException  ItemNotFoundException_  {color:#ff}_ + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands. CopyI CopyI_{color}  temCommand _temCommand_  _ [Pipeline] } _   _  [Pipeline] //  ws  ws_   _  [Pipeline] } _   _  [Pipeline] //  node  node_   _  [Pipeline] End of  Pipeline  Pipeline_   Finished  _Finished :  {color:#ff}  SUCCESS {color}_  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-50456) Pipeline continues after powershell error

2018-03-28 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50456  
 
 
  Pipeline continues after powershell error   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 

  
 
 
 
 

 
 Pipeline script continues after errors in powershell script.Pipeline (none of the mentioned files exist!):node("...") \{    ws("x:\ \ src") \{        powershell 'Copy-Item "a.xml" -Destination "b.xml"'    }}output:[Pipeline] \{[Pipeline] wsRunning in x:\src[Pipeline] \{[Pipeline] powershell[src] Running PowerShell scriptpowershell.exe : Copy-Item : Cannot find path 'X:\src\a.xml' because it does not exist.At X:\src@tmp\durable-472cdca6\powershellWrapper.ps1:5 char:3+   & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Fi ...+   ~~~+ CategoryInfo  : NotSpecified: (Copy-Item : Can...does not exist.:String) [], RemoteException+ FullyQualifiedErrorId : NativeCommandErrorAt X:\src@tmp\durable-472cdca6\powershellScript.ps1:1 char:1+ Copy-Item "a.xml" -Destination "b.xml"+ ~~+ CategoryInfo  : ObjectNotFound: (X:\src\a.xml:String) [Copy-Item    ], ItemNotFoundException+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyI    temCommand   [Pipeline] }[Pipeline] // ws[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-50456) Pipeline continues after powershell error

2018-03-28 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50456  
 
 
  Pipeline continues after powershell error   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 durable-task-plugin  
 
 
Created: 
 2018-03-28 12:50  
 
 
Environment: 
 jenkins 2.89.4, durable-task-plugin 1.22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Wouter Slob  
 

  
 
 
 
 

 
 Pipeline script continues after errors in powershell script. Pipeline (none of the mentioned files exist!): node("...") {     ws("x:src") {         powershell 'Copy-Item "a.xml" -Destination "b.xml"'     } } output: [Pipeline] { [Pipeline] ws Running in x:\src [Pipeline] { [Pipeline] powershell [src] Running PowerShell script powershell.exe : Copy-Item : Cannot find path 'X:\src\a.xml' because it does not exist. At X:\src@tmp\durable-472cdca6\powershellWrapper.ps1:5 char:3 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Fi ... + ~~~ + CategoryInfo : NotSpecified: (Copy-Item : Can...does not exist. :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError At X:\src@tmp\durable-472cdca6\powershellScript.ps1:1 char:1 + Copy-Item "a.xml" -Destination "b.xml" + ~~  + CategoryInfo : ObjectNotFound: (X:\src\a.xml:String) [Copy-Item   ], ItemNotFoundException  + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyI   temCommand [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS

[JIRA] (JENKINS-50029) Powershell treats warnings as errors

2018-03-08 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob commented on  JENKINS-50029  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Powershell treats warnings as errors   
 

  
 
 
 
 

 
 Thnx Sam Van Oort & Gabriel Loewen for prompt response and explanation. I'm looking forward to testing the upcoming patch.   I'm not sure if it is related to the same plugin, but yesterday I've created another issue: JENKINS-49986. You might want to have a quick look at that one     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49986) Pipeline 'bat' hangs on ws with forward slash path separator

2018-03-08 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob commented on  JENKINS-49986  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline 'bat' hangs on ws with forward slash path separator   
 

  
 
 
 
 

 
 After installing today's updates I'm now getting a NullPointerException on the first bat from my example. Output: 

java.lang.NullPointerException at hudson.FilePath.sibling(FilePath.java:1258) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.tempDir(FileMonitoringTask.java:237) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:121) at org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.(WindowsBatchScript.java:94) at org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.(WindowsBatchScript.java:92) at org.jenkinsci.plugins.durabletask.WindowsBatchScript.doLaunch(WindowsBatchScript.java:60) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launchWithCookie(FileMonitoringTask.java:76) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:71) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:176) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) at WorkflowScript.run(WorkflowScript:16) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor299.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) at

[JIRA] (JENKINS-50029) Powershell treats warnings as errors

2018-03-08 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50029  
 
 
  Powershell treats warnings as errors   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 

  
 
 
 
 

 
 After upgrading to the latest Jenkins LTS & durable task plugin (v1.21) our pipelines fail on warnings.Pipeline:{code:java}node() {bat 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'powershell 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'}{code}{quote}Output: 2018-03-08 19:47:13 [src] Running batch script 2018-03-08 19:47:14  2018-03-08 19:47:14 d:\src>C:\Python27\python.exe -c "import warnings;warnings.warn('future', FutureWarning)"  2018-03-08 19:47:17 -c:1: FutureWarning: future [Pipeline] powershell {color:#ff}2018-03-08 19:47:18 [src] Running PowerShell script{color} {color:#ff} 2018-03-08 19:47:20 powershell.exe : -c:1: FutureWarning: future{color} {color:#ff} 2018-03-08 19:47:20 At D:\src@tmp\durable-4343e8b5\powershellWrapper.ps1:3 char:1{color} {color:#ff} 2018-03-08 19:47:20 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -File ...{color} {color:#ff} 2018-03-08 19:47:20 + ~{color} {color:#ff} 2018-03-08 19:47:20 + CategoryInfo : NotSpecified: (-c:1: FutureWarning: future:Strin g) [], RemoteException{color} {color:#ff} 2018-03-08 19:47:20 + FullyQualifiedErrorId : NativeCommandError{color} {color:#ff} 2018-03-08 19:47:20{color}{quote} This returns in "1" exit code, causing the pipeline to fail. So somehow, somewhere, the warning is transformed / interpreted as an error.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
 

[JIRA] (JENKINS-50029) Powershell treats warnings as errors

2018-03-08 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50029  
 
 
  Powershell treats warnings as errors   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 
 
Assignee: 
 Sam Van Oort  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-50029) Powershell treats warnings as errors

2018-03-08 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50029  
 
 
  Powershell treats warnings as errors   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 durable-task-plugin  
 
 
Created: 
 2018-03-08 18:58  
 
 
Environment: 
 Latest Jenkins LTS, Durable-task plugin v2.21  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Wouter Slob  
 

  
 
 
 
 

 
 After upgrading to the latest Jenkins LTS & durable task plugin (v1.21) our pipelines fail on warnings. Pipeline: 

 

node() {
bat 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'

powershell 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'
}
 

 

Output: 2018-03-08 19:47:13 [src] Running batch script 2018-03-08 19:47:14  2018-03-08 19:47:14 d:\src>C:\Python27\python.exe -c "import warnings;warnings.warn('future', FutureWarning)"  2018-03-08 19:47:17 -c:1: FutureWarning: future [Pipeline] powershell 2018-03-08 19:47:18 [src] Running PowerShell script  2018-03-08 19:47:20 powershell.exe : -c:1: FutureWarning: future  2018-03-08 19:47:20 At D:\src@tmp\durable-4343e8b5\powershellWrapper.ps1:3 char:1  2018-03-08 19:47:20 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -File ...  2018-03-08 19:47:20 + ~  2018-03-08 19:47:20 + CategoryInfo : NotSpecified: (-c:1: FutureWarning: future:Strin g) [],

[JIRA] (JENKINS-49986) Pipeline 'bat' hangs on ws with forward slash path separator

2018-03-07 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49986  
 
 
  Pipeline 'bat' hangs on ws with forward slash path separator   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49986) Pipeline 'bat' hangs on ws with forward slash path separator

2018-03-07 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49986  
 
 
  Pipeline 'bat' hangs on ws with forward slash path separator   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 

  
 
 
 
 

 
 After upgrading Jenkins LTS (from 2.89.2 to 2.89.4) and several plugins yesterday we have an issue with hanging "bat" commands on windows nodes.The following pipeline illustrates the issue:{code:java}node() {ws( " ' D:\\ " ' ) {bat 'echo Hello 1'}ws( " ' D:/ " ' ) {bat 'echo Hello 2'}}{code}The output is:{quote}Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on XXX in C:\Jenkins\workspace\YYY [Pipeline] \{ [Pipeline] ws Running in D:\src [Pipeline] \{ [Pipeline] bat [src] Running batch scriptD:\src>echo Hello 1  Hello 1 [Pipeline] } [Pipeline] // ws [Pipeline] ws Running in D:/src [Pipeline] \{ [Pipeline] bat [D:/src] Running batch scriptD:\src>echo Hello 2  Hello 2{quote}And the pipeline hangs here / does not finish ever.So it looks like setting a workspace with a path containing a forward slash does not work anymore with bat commands.I also tried the powershell command and that works without issues.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-49986) Pipeline 'bat' hangs on ws with forward slash path separator

2018-03-07 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49986  
 
 
  Pipeline 'bat' hangs on ws with forward slash path separator   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 

  
 
 
 
 

 
 After upgrading Jenkins LTS (from 2.89.2 to 2.89.4) and several plugins yesterday we have an issue with hanging "bat" commands on windows nodes.The following pipeline illustrates the issue:{code:java}node() {ws("D:\\") {bat 'echo Hello 1'}ws("D:/") {bat 'echo Hello 2'}}{code}The output is:  {quote} Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on XXX in C:\Jenkins\workspace\YYY[Pipeline] \{[Pipeline] wsRunning in D:\src[Pipeline] \{[Pipeline] bat[src] Running batch scriptD:\src>echo Hello 1 Hello 1[Pipeline] }[Pipeline] // ws[Pipeline] wsRunning in D:/src[Pipeline] \{[Pipeline] bat[D:/src] Running batch scriptD:\src>echo Hello 2 Hello 2 {quote} And the pipeline hangs here / does not finish ever.So it looks like setting a workspace with a path containing a forward slash does not work anymore with bat commands.I also tried the powershell command and that works without issues.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-49986) Pipeline 'bat' hangs on ws with forward slash path separator

2018-03-07 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49986  
 
 
  Pipeline 'bat' hangs on ws with forward slash path separator   
 

  
 
 
 
 

 
Change By: 
 Wouter Slob  
 
 
Summary: 
 Pipelin Pipeline '  bat '  hangs on ws with forward slash path separator  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google 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-49986) Pipelin bat hangs on ws with forward slash path separator

2018-03-07 Thread wouter.s...@ortec.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Wouter Slob created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49986  
 
 
  Pipelin bat hangs on ws with forward slash path separator   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 durable-task-plugin  
 
 
Created: 
 2018-03-07 12:48  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Wouter Slob  
 

  
 
 
 
 

 
 After upgrading Jenkins LTS (from 2.89.2 to 2.89.4) and several plugins yesterday we have an issue with hanging "bat" commands on windows nodes. The following pipeline illustrates the issue: 

 

node() {
ws("D:\\") {
bat 'echo Hello 1'
}

ws("D:/") {
bat 'echo Hello 2'
}
}
 

 The output is: Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Running on XXX in C:\Jenkins\workspace\YYY [Pipeline] { [Pipeline] ws Running in D:\src [Pipeline] { [Pipeline] bat [src] Running batch script D:\src>echo Hello 1  Hello 1 [Pipeline] } [Pipeline] // ws [Pipeline] ws Running in D:/src [Pipeline] { [Pipeline] bat [D:/src] Running batch script D:\src>echo Hello 2  Hello 2 And the pipeline hangs here / does not finish ever. So it looks like setting a workspace with a path containing a forward slash does not work anymore with bat commands. I also tried the powershell command and that works without issues.