Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47021

Triggering of downstream projects doesn't work in Maven Project Plugin since 2.14

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      "Triggering of downstream projects" stopped working since 2.14 and further, works fine in 2.13.

      Tested on jenkins clean install.

        Attachments

          Activity

          Hide
          triplesub Russ Hayward added a comment - - edited

          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 RH-47021.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.

           

          Show
          triplesub Russ Hayward added a comment - - edited 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 RH-47021.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.  

            People

            • Assignee:
              Unassigned
              Reporter:
              mgrybyk Mykola Grybyk
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: