Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to include jenkins-build-monitor-plugin as dependency because of missing parent POM for jenkins-build-monitor #373

Open
stefanverhoeff opened this issue May 22, 2018 · 9 comments · May be fixed by #374

Comments

@stefanverhoeff
Copy link

commented May 22, 2018

This 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.

@GhaTMA

This comment has been minimized.

Copy link

commented May 23, 2018

Similar case here!
We use gradle to test our Job DSL scripts before running them on Jenkins. We use this kind of project https://github.com/jenkinsci/job-dsl-plugin/wiki/Testing-DSL-Scripts and it requires the dependency on your plugin. We are stuck with the error mentioned before about missing parent pom!

@jan-molak

This comment has been minimized.

Copy link
Owner

commented May 24, 2018

Hi there,

I'm happy to publish the parent pom if that helps? Alternatively if someone wants to propose a PR to refactor the plugin POM I'd be happy to consider that option.

Jan

@stefanverhoeff

This comment has been minimized.

Copy link
Author

commented May 25, 2018

Hi @jan-molak, thanks for the response. Publishing the parent POM would be the easiest fix now and can fix the issue retroactively for existing versions.

Meanwhile I'll try to do a refactoring on the POM structure.

UnsafePointer added a commit to UnsafePointer/jenkins-build-monitor-plugin that referenced this issue May 25, 2018
stefanverhoeff added a commit to UnsafePointer/jenkins-build-monitor-plugin that referenced this issue May 25, 2018
@GhaTMA

This comment has been minimized.

Copy link

commented Jun 13, 2018

any plans when the parent POM would be published, or when this fix would be released?

@sebastiangraf

This comment has been minimized.

Copy link

commented Sep 17, 2018

PR #374 is done and reviewed, any plans to merge this? We are facing broken builds each time this plugin is updated.

@starwarsfan

This comment has been minimized.

Copy link

commented Oct 9, 2018

Any news here? Any other open points regarding #374? The problem still exists!

@starwarsfan

This comment has been minimized.

Copy link

commented Feb 26, 2019

More than four months...

Any news at this topic?

@jan-molak

This comment has been minimized.

Copy link
Owner

commented Feb 26, 2019

Hey @stefanverhoeff - you're right, it's been a good couple of months since I had the capacity to look at the tickets and PRs you guys have raised. In that time the CloudBees Dev@Cloud service I used for Build Monitor has also ceased to exist, which means that I'll need to set up the pipeline from scratch again somewhere else.

@stefanverhoeff

This comment has been minimized.

Copy link
Author

commented Mar 4, 2019

Hi @jan-molak , no worries. For publishing the parent POM at least no extra CI should be needed? Or was that part automated on Dev@Cloud?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.