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

"Build modules as separate jobs" fails to run Post-build Actions correctly

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • ivy-plugin
    • Jenkins ver. 1.430
      Ivy Plugin 1.19
      Gerrit Trigger 2.3.1

      When using Ivy Plugin and Build modules as separate jobs setting is used the plugin fails to run Post-build Actions correctly.

      This happens immediately when job starts:

      Parsing Ivy Descriptor Files
      Triggering acme:module1
      Triggering acme:module2
      Triggering acme:module3
      Notifying upstream projects of job completion
      Finished: SUCCESS
      

      Note that build is immediately reported as SUCCESS even though none of the modules are not yet finished (or maybe even started). When some of the modules fails main job's status is correctly changed to FAILED but no post-build actions are triggered. This is also the case when all the modules are built successfully: status is SUCCESS but no post-build actions are triggered.

      We are using Ivy Plugin + Gerrit Trigger. Now what happens is that Gerrit correctly gets information about starting the job but it also immediately sets change's status to Verfified because build was successful. This means that in Gerrit we can see that review is started by Jenkins and it is always Verfified.

      We would like to see that the main job would run as long as module jobs are running. When every module job that should run (we are using Incremental build setting, too) has finished building only then should the main job report its status and trigger post-build actions (and in our case notify Gerrit if the build was successful or not).

          [JENKINS-11331] "Build modules as separate jobs" fails to run Post-build Actions correctly

          temeq created issue -
          temeq made changes -
          Description Original: When using Ivy Plugin and _Build modules as separate jobs_ setting is used the plugin fails to run Post-build Actions.

          This happens *immediately* when job starts:
          {noformat}
          Parsing Ivy Descriptor Files
          Triggering acme:module1
          Triggering acme:module2
          Triggering acme:module3
          Notifying upstream projects of job completion
          Finished: SUCCESS
          {noformat}
          Note that build is immediately reported as {{SUCCESS}} even though none of the modules are not yet finished (or maybe even started). When some of the modules fails main job's status is correctly changed to {{FAILED}} but no post-build actions are triggered. This is also the case when all the modules are built successfully: status is {{SUCCESS}} but no post-build actions are triggered.

          We are using Ivy Plugin + Gerrit Trigger. Now what happens is that Gerrit correctly gets information about starting the job but it doesn't receive *any kind* of ending information. This means that in Gerrit we can see that review is started by Jenkins but it is *never* finished.

          We would like to see that the main job would run as long as module jobs are running. When every module job that should run (we are using _Incremental build_ setting, too) has finished building only then should the main job report its status and trigger post-build actions (and in our case notify Gerrit if the build was successful or not).
          New: When using Ivy Plugin and _Build modules as separate jobs_ setting is used the plugin fails to run Post-build Actions.

          This happens *immediately* when job starts:
          {noformat}
          Parsing Ivy Descriptor Files
          Triggering acme:module1
          Triggering acme:module2
          Triggering acme:module3
          Notifying upstream projects of job completion
          Finished: SUCCESS
          {noformat}
          Note that build is immediately reported as {{SUCCESS}} even though none of the modules are not yet finished (or maybe even started). When some of the modules fails main job's status is correctly changed to {{FAILED}} but no post-build actions are triggered. This is also the case when all the modules are built successfully: status is {{SUCCESS}} but no post-build actions are triggered.

          We are using Ivy Plugin + Gerrit Trigger. Now what happens is that Gerrit correctly gets information about starting the job but it also immediately sets change's status to *Verfified* because build was successful. This means that in Gerrit we can see that review is started by Jenkins and it is *always Verfified*.

          We would like to see that the main job would run as long as module jobs are running. When every module job that should run (we are using _Incremental build_ setting, too) has finished building only then should the main job report its status and trigger post-build actions (and in our case notify Gerrit if the build was successful or not).
          temeq made changes -
          Description Original: When using Ivy Plugin and _Build modules as separate jobs_ setting is used the plugin fails to run Post-build Actions.

          This happens *immediately* when job starts:
          {noformat}
          Parsing Ivy Descriptor Files
          Triggering acme:module1
          Triggering acme:module2
          Triggering acme:module3
          Notifying upstream projects of job completion
          Finished: SUCCESS
          {noformat}
          Note that build is immediately reported as {{SUCCESS}} even though none of the modules are not yet finished (or maybe even started). When some of the modules fails main job's status is correctly changed to {{FAILED}} but no post-build actions are triggered. This is also the case when all the modules are built successfully: status is {{SUCCESS}} but no post-build actions are triggered.

          We are using Ivy Plugin + Gerrit Trigger. Now what happens is that Gerrit correctly gets information about starting the job but it also immediately sets change's status to *Verfified* because build was successful. This means that in Gerrit we can see that review is started by Jenkins and it is *always Verfified*.

          We would like to see that the main job would run as long as module jobs are running. When every module job that should run (we are using _Incremental build_ setting, too) has finished building only then should the main job report its status and trigger post-build actions (and in our case notify Gerrit if the build was successful or not).
          New: When using Ivy Plugin and _Build modules as separate jobs_ setting is used the plugin fails to run Post-build Actions correctly.

          This happens *immediately* when job starts:
          {noformat}
          Parsing Ivy Descriptor Files
          Triggering acme:module1
          Triggering acme:module2
          Triggering acme:module3
          Notifying upstream projects of job completion
          Finished: SUCCESS
          {noformat}
          Note that build is immediately reported as {{SUCCESS}} even though none of the modules are not yet finished (or maybe even started). When some of the modules fails main job's status is correctly changed to {{FAILED}} but no post-build actions are triggered. This is also the case when all the modules are built successfully: status is {{SUCCESS}} but no post-build actions are triggered.

          We are using Ivy Plugin + Gerrit Trigger. Now what happens is that Gerrit correctly gets information about starting the job but it also immediately sets change's status to *Verfified* because build was successful. This means that in Gerrit we can see that review is started by Jenkins and it is *always Verfified*.

          We would like to see that the main job would run as long as module jobs are running. When every module job that should run (we are using _Incremental build_ setting, too) has finished building only then should the main job report its status and trigger post-build actions (and in our case notify Gerrit if the build was successful or not).
          Summary Original: "Build modules as separate jobs" fails to run Post-build Actions New: "Build modules as separate jobs" fails to run Post-build Actions correctly
          Paul Woodward made changes -
          Labels New: ivy plugin
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 141550 ] New: JNJira + In-Review [ 175503 ]

            tbingaman Timothy Bingaman
            teqvick temeq
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: