[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Stefan Verhoeff commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin We have the same issue, using the build-monitor-plugin as dependency with Gradle. It's reported to the project's GitHub project: https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/373 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Edd Grant commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin Hey Daniel Spilker, Yep we originally tested that build as it happens, double checked it again this morning and got the same error: > 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. > Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.12+build.201708172343. > Could not parse POM https://nexus-build.tax.service.gov.uk/content/groups/public/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. Interestingly I cloned the build-monitor-plugin repository, changed the version to 1.12-SNAPSHOT and ran a mvn install. I then was able to get Gradle to use this artefact just fine by using mavenLocal(). This confused me as I was expecting to get the same error I got when pulling the official artefact, could it be that there's something going on in the publishing phase which is modifying the pom? Cheers! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin Has anyone tested the lasted version v1.12+build.201708172343? The POM seems to be fixed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Edd Grant commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin This is affecting us too. Whilst I agree with Daniel Spilker that it is not directly a Job DSL issue, it does manifest when trying to write Job DSL tests, since following the Testing DSL Scripts guidance and trying to resolve this plugin causes this issue to manifest. Would it be possible to get the maintainer of the build-monitor-plugin to make the necessary changes to the POM to fix this issue? It sounds like the steps are well laid out above and it would stop others from hitting this issue (I've just spent a good couple of hours trying to figure out what was wrong). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin This is not a Job DSL issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-43171 Correct Pom for build-monitor-plugin Change By: Daniel Spilker Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-43171 Correct Pom for build-monitor-plugin Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title
Chaz Ruhl created an issue
Jenkins / JENKINS-43171
Correct Pom for build-monitor-plugin
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
build-monitor-plugin, job-dsl-plugin
Created:
2017/Mar/28 5:53 PM
Environment:
Jenkins-2.32.3 gradle - 2.12 build-monitor-plugin-1.11+build.201701152243 job-dsl-plugin - 1.58
Priority:
Minor
Reporter:
Chaz Ruhl
We run tests against our job-dsl code using gradle before kicking off the dsl processing job. For dsl code referencing various plugins, we include the dependancies via build.gradle dependancies { testPlugins 'org.jenkins-ci.main:maven-plugin:2.3' } when including build-monitor-plugin: testPlugins 'org.jenkins-ci.plugins:build-monitor-plugin:1.11+build.201701152243' I get an error saying: > Could not resolve org.jenkins-ci.plugins:build-monitor-plugin:1.11+build.201701152243. > Could not parse POM http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/1.11+build.201701152243/build-monitor-plugin-1.11+build.201701152243.pom > Could not find org.jenkins-ci.plugins:build-monitor:1.11+build.201701152243. After a little digging, it appears the pom is not set-up per https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-pom.xml I was able to add the pom & hpi to our local repository and successfully got the tests running by making the following changes: org.jenkins-ci.plugins plugin 1.609.3 This was set to build-monitor - which doesn't seem to exist. With the required jenkins version in the correct place (the parent), a separate verison tag needs to be added: 1.11+build.201701152243 A version for the hamcrest dependancy was needed for it to be correctly found org.hamcrest hamcrest-all 3.1 test
