-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major
-
Component/s: p4-plugin
-
None
-
Environment:Jenkins pipeline with
In my Jenkins pipeline script, I invoke cleanup(true) as stated per Perforce documentation. With the upgrade to p4-plugin version 1.17.3 (from 1.17.2), the following broke my pipeline scritps:
341 cleanup {
342 cleanup(true)
343 }
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 342: Step does not take a single required parameter - use named parameters instead @ line 342, column 13.
cleanup(true)
^
1 error
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1107)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:624)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:602)
at org.codehaus.groovy.corg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 342: Step does not take a single required parameter - use named parameters instead @ line 342, column 13.
cleanup(true)
^1 error at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:309)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1107)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:624)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:602)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:579)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:323)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:293)ontrol.CompilationUnit.compile(CompilationUnit.java:579)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:323)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:293)
Likely you intended to remove this with some kind of auto-cleanup mechanism eluded to by the release notes / features that went into that release. However, I can't seem to find any documentation to correct this issue at hand. Likely, you'd also want to update the documentation and send people a note to be aware of this issue on upgrades.
