-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Linux Jenkins 1.647 Pipeline Plugin 1.13
I have a maven project that uses Jaxb to load a schema document and generate something from it. This project fails with:
[ERROR] [ERROR] schema_reference.4: Failed to read schema document 'file:/apps/.jenkins/workspace/project/feature%2FmyFeature/somePath/src/main/resources/MySchema.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>.
[ERROR] unknown location
[ERROR]
Likewise, I have a project with unit tests that read in a file from the filesystem, make modifications, and write it back out. However, these test fail seemingly because the file can't be written out.
When I change my feature branch name from "feature/myFeature" to just "myFeature" the projects succeed in building.
- depends on
-
-
- Closed
-
[JENKINS-32902] Multibranch pipeline has issues with / in jobName
| Link |
New:
This issue depends on |
| Description |
New:
I have a maven project that uses Jaxb to load a schema document and generate something from it. This project fails with: [ERROR] [ERROR] schema_reference.4: Failed to read schema document 'file:/apps/.jenkins/workspace/project/feature%2FmyFeature/somePath/src/main/resources/MySchema.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. [ERROR] unknown location [ERROR] Likewise, I have a project with unit tests that read in a file from the filesystem, make modifications, and write it back out. However, these test fail seemingly because the file can't be written out. When I change my feature branch name from "feature/myFeature" to just "myFeature" the projects succeed in building. |
| Environment | Original: Linux | New: Linux Jenkins 1.647 Pipeline Plugin 1.13 |
| Resolution | New: Not A Defect [ 7 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Granted, there could be an issue in one of the maven plugins... However, this project builds fine as a Jenkins maven project, or by executing mvn install from a command line. Because of that, this is a defect in the pipeline plugin. When a "new" plugin produces different behavior to builds that already work with the underlying software (Jenkins and Maven) then I do believe it is a defect with the plugin.
Ok, on second thought. We probably didn't ever need to build with a "/" in the directory name. I'll give that a try and see if it fails in a normal build.
| Workflow | Original: JNJira [ 168609 ] | New: JNJira + In-Review [ 198446 ] |
| Component/s | New: pipeline-general [ 21692 ] |
A bug in your Maven plugin, unit test, etc., not in Jenkins. A typical mistake would be using File.toURL, which is known to be broken (use toURI instead, or toPath() if you can assume Java 7+).