-
Bug
-
Resolution: Fixed
-
Major
-
None
Using load step to load two different groovy files without an explicit class but the same package declaration, causes Jenkins to fail during startup process if the build should be resumed.
For example, create a dummy pipeline like
def util def config def util2 node('master') { sh 'cp -r /tmp/test/src .' config = load 'src/org/foo/devops/JenkinsEnvironment.groovy' util = load 'src/org/foo/devops/Utility.groovy' config.loadProdConfiguration() } util.isValueExist("") echo "kill me while I'm sleeping" sleep 20 node('master') { util2 = load 'src/org/foo/devops/Utility.groovy' util = load 'src/org/foo/devops/Utility.groovy' }
And copy the two attached files at /tmp/test/src/org/foo/devops/
(Files can be retrieved as you prefer)
Build the job and restart jenkins while is building.
Then you won't be able to access Jenkins.
- is blocking
-
JENKINS-50174 pipeline job status page cannot be rendered properly if a build hits JENKINS-50171
- Resolved
- is duplicated by
-
JENKINS-50174 pipeline job status page cannot be rendered properly if a build hits JENKINS-50171
- Resolved
-
JENKINS-50172 load step doesn't generate unique name for classes
- Resolved
- is related to
-
JENKINS-50172 load step doesn't generate unique name for classes
- Resolved
- links to