[JIRA] (JENKINS-47021) Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
Title: Message Title
Russ Hayward edited a comment on JENKINS-47021
Re: Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
We have come across this issue today and it makes the plugin unusable for us. We have had to revert to version 2.13.The problem was caused by this change ( - JENKINS-34789 - ):[https://github.com/jenkinsci/maven-plugin/commit/40d36bfc75b406acf290e0a439f681a690250e2a]I think this means that if a project does not contain a snapshot dependency it will never trigger a downstream project. I have tested this in a clean Jenkins with the projects contained in the attachment JENKINS RH -47021 -RH .zip. They were both set up with the default configuration and goals "clean install". I would expect building ProjectA to trigger a build of ProjectB, but it does not.I have patched the latest release of the plugin to remove the change above and then building ProjectA triggers a build of ProjectB. I commented the following lines:// // Check to see if is a release so we don't trigger the downstream project // else if (mavenModuleSetBuild != null && mavenModuleSetBuild.isRelease()) \{ // return false; // }Let me know if you need any more information.
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-47021) Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
Title: Message Title Russ Hayward updated an issue Jenkins / JENKINS-47021 Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14 Change By: Russ Hayward Attachment: JENKINS-47021-RH.zip 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-47021) Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
Title: Message Title Russ Hayward updated an issue Jenkins / JENKINS-47021 Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14 Change By: Russ Hayward Attachment: RH-47021.zip 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-47021) Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
Title: Message Title
Russ Hayward edited a comment on JENKINS-47021
Re: Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
We have come across this issue today and it makes the plugin unusable for us. We have had to revert to version 2.13.The problem was caused by this change (JENKINS-34789) :[https://github.com/jenkinsci/maven-plugin/commit/40d36bfc75b406acf290e0a439f681a690250e2a]I think this means that if a project does not contain a snapshot dependency it will never trigger a downstream project. I have tested this in a clean Jenkins with the projects contained in the attachment JENKINS-47021-RH.zip. They were both set up with the default configuration and goals "clean install". I would expect building ProjectA to trigger a build of ProjectB, but it does not.I have patched the latest release of the plugin to remove the change above and then building ProjectA triggers a build of ProjectB. I commented the following lines:// // Check to see if is a release so we don't trigger the downstream project// else if (mavenModuleSetBuild != null && mavenModuleSetBuild.isRelease()) \{// return false;// }Let me know if you need any more information.
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-47021) Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
Title: Message Title Russ Hayward updated an issue Jenkins / JENKINS-47021 Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14 Change By: Russ Hayward Attachment: JENKINS-47021-RH.zip 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-47021) Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
Title: Message Title
Russ Hayward commented on JENKINS-47021
Re: Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14
We have come across this issue today and it makes the plugin unusable for us. We have had to revert to version 2.13. The problem was caused by this change: https://github.com/jenkinsci/maven-plugin/commit/40d36bfc75b406acf290e0a439f681a690250e2a I think this means that if a project does not contain a snapshot dependency it will never trigger a downstream project. I have tested this in a clean Jenkins with the projects contained in the attachment JENKINS-47021-RH.zip. They were both set up with the default configuration and goals "clean install". I would expect building ProjectA to trigger a build of ProjectB, but it does not. I have patched the latest release of the plugin to remove the change above and then building ProjectA triggers a build of ProjectB. I commented the following lines: // // Check to see if is a release so we don't trigger the downstream project // else if (mavenModuleSetBuild != null && mavenModuleSetBuild.isRelease()) { // return false; // } Let me know if you need any more information.
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.
