When using a Scripted Pipeline, using the node-Block creates a workspace and ensures that the workspace is only used by one build (by appending e.g. @2 )
When using a Declarative Jenkins-Pipeline, this seems not to be the case.
Even when using
only one workspace is created, nothing is appended to the workspace-name.
Is that inteded behaviour?
I can work around this by using the customWorkspace parameter, but it is a changed behaviour in comparison to the old Jenkinsfiles.