-
Bug
-
Resolution: Fixed
-
Major
-
None
Hi,
I'm using the Job DSL plug-in from another plug-in, and need to use it for my integration tests as well:
dependencies {
...
jenkinsPlugins 'org.jenkins-ci.plugins:job-dsl:1.32@jar'
...
}
I'm using the JenkinsRule and it fails because it cannot resolve job-dsl:1.32. After looking into the code of JenkinsRule, I've seen that the JAR location is fetched using Manifest information, in the Short-Name attribute.
Although this information is filled in correctly in the JPI file, it is absent in the JAR file. I had a look at other plug-ins, and the manifest information is generated for both the JAR and the HPI/JPI file. So it might have something to do with the Gradle JPI plug-in.
In order to make the Job DSL plug-in useable from other plug-ins, especially in their integration tests using the JenkinsRule, the JAR needs the Manifest information.
Best regards,
Damien.
[JENKINS-27994] The Manifest of the job-dsl JAR is empty, making it unuseable for tests
Damien Coraboeuf
created issue -
Damien Coraboeuf
made changes -
| Component/s | New: gradle-jpi-plugin [ 16321 ] |
Daniel Spilker
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Daniel Spilker
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 162595 ] | New: JNJira + In-Review [ 208697 ] |
