Unable to include jenkins-build-monitor-plugin as dependency because of missing parent POM for jenkins-build-monitor
See original GitHub issueThis issue is similar to #299 and JENKINS-43171.
We’re using the Job DSL plugin and Gradle Jenkins Job DSL plugin to automatically create Jenkins jobs. To generate the right XML, the Job DSL plugin uses the Jenkins plugin as dependency.
We are using Gradle to include dependencies, when we run Gradle it complains the parent POM is missing:
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all files for configuration ':jenkinsPlugins'.
> Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.12+build.201708172343.
Required by:
project :
> Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.12+build.201708172343.
> Could not parse POM https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/1.12+build.201708172343/build-monitor-plugin-1.12+build.201708172343.pom
> Could not find org.jenkins-ci.plugins:build-monitor:1.12+build.201708172343.
Searched in the following locations:
https://repo1.maven.org/maven2/org/jenkins-ci/plugins/build-monitor/1.12+build.201708172343/build-monitor-1.12+build.201708172343.pom
https://repo1.maven.org/maven2/org/jenkins-ci/plugins/build-monitor/1.12+build.201708172343/build-monitor-1.12+build.201708172343.jar
https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor/1.12+build.201708172343/build-monitor-1.12+build.201708172343.pom
https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor/1.12+build.201708172343/build-monitor-1.12+build.201708172343.jar
https://plugins.gradle.org/m2/org/jenkins-ci/plugins/build-monitor/1.12+build.201708172343/build-monitor-1.12+build.201708172343.pom
https://plugins.gradle.org/m2/org/jenkins-ci/plugins/build-monitor/1.12+build.201708172343/build-monitor-1.12+build.201708172343.jar
This is the snippet of Gradle code where we include the plugin:
dependencies {
...
jenkinsPlugins 'org.jenkins-ci.plugins:build-monitor-plugin:1.12+build.201708172343'
...
}
Indeed the parent POM is not in the Jenkins maven repository. Fix could be to either publish the parent POM or to refactor the plugin POM (this is suggested in JENKINS-43171). Internally we have published the plugin and parent POMs in our private maven repository.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Jenkins Fails to parse poms due to missing parent pom
I was facing this issue after upgrading from Jenkins "1.651.3" to "2.346.3 LTS". When I created a bright new job (without copy) -...
Read more >Spring Boot Maven Plugin Documentation
A dependency management section, inherited from the spring-boot-dependencies POM, that manages the versions of common dependencies. This ...
Read more >symptom - MuleSoft Help Center
This error is caused by the Mule application not reading the HTTP connector dependency in a parent pom.
Read more >Understanding Maven's “relativePath” Tag for a Parent POM
In this article, we learned that Maven does not resolve parent POMs by searching Maven repositories firstly. It rather searches for it locally, ......
Read more >Maven Getting Started Guide
You've probably already noticed a dependencies element in the POM we've been using as an example. You have, in fact, been using an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
any plans when the parent POM would be published, or when this fix would be released?
Any news here? Any other open points regarding #374? The problem still exists!