I'm migrating an old Jenkins buildserver i did not set up to a new updated version and that broke the groovy scripts since it's not naming folders in the @libs the same way it did before, maybe it's some setting that is changed.
@lib structure on the old Jenkins 2.204:
D:\jenkins_workspace\<name of workspace>@libs\PC_Lib\PC_Scripts
on the new install with Jenkins 2.361 the @lib looks like this:
D:\jenkins_workspace\<name of workspace>@libs\46cbfc656d3cc901a720a5a9085086f64d931aaa512386cb7be1cd2ca870a4ed\PC_Scripts
The setup: Windows server 2022 Jenkins 2.361.1 SCM = Subversion (SVN) 1.8
In Groovy files they refer to the script like this:
def SCRIPT_PATH = "${env.WORKSPACE}@libs/PC_Lib/PC_Scripts"
Is there any way of using the old way with the direct naming of the library name instead of the UUID name?