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

Maven build finished success but Jenkins job mark build as unstable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • maven-plugin
    • Jenkins master, Jenkins slave, Java 1.7
      Jenkins version - 1.596.2 LTS
      Maven version - 3.2.5
      Maven plugin version - 2.9
      Jenkins job type in use - Maven job

      Running the following Maven build step:

      clean install -e -U

      (note that we are using the workaround described here - https://issues.jenkins-ci.org/browse/JENKINS-22486 to have multi threaded builds).

      The output of the maven build step is as follows (note that the first line in the console just after the SUCCESS summary is_ [JENKINS] Archiving_):

      11:37:13 [INFO] ------------------------------------------------------------------------
      11:37:13 [INFO] BUILD SUCCESS
      11:37:13 [INFO] ------------------------------------------------------------------------
      11:37:13 [INFO] Total time: 15:47 min (Wall Clock)
      11:37:13 [INFO] Finished at: 2015-06-15T11:37:13+03:00
      11:37:15 [INFO] Final Memory: 405M/934M
      11:37:15 [INFO] ------------------------------------------------------------------------
      11:37:15 [JENKINS] Archiving

      But at the end of the console we get:

      11:38:46 channel stopped
      11:38:53 Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.

      This job runs successfully most of the times. When it successfully done, the first line after the success summary is:

      12:27:13 Waiting for Jenkins to finish collecting data

      Regarding the job configuration - the first thing after the maven step is the Post step section, configured only if the build succeeds

          [JENKINS-28904] Maven build finished success but Jenkins job mark build as unstable

          Maty Grosz added a comment - - edited

          I am getting this error too many times. It blocks the CI process. Anyone?

          Maty Grosz added a comment - - edited I am getting this error too many times. It blocks the CI process. Anyone?

          Jan Vodolan added a comment -

          Confirm same behavior... 
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 03:53 min
          [INFO] Finished at: 2017-05-13T00:12:02+02:00
          [INFO] Final Memory: 139M/808M
          [INFO] ------------------------------------------------------------------------
          Waiting for Jenkins to finish collecting data
          channel stopped
          Not sending mail to unregistered user xxx@xxx.cz
          An attempt to send an e-mail to empty list of recipients, ignored.
          Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered

          Jan Vodolan added a comment - Confirm same behavior...  [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 03:53 min [INFO] Finished at: 2017-05-13T00:12:02+02:00 [INFO] Final Memory: 139M/808M [INFO] ------------------------------------------------------------------------ Waiting for Jenkins to finish collecting data channel stopped Not sending mail to unregistered user xxx@xxx.cz An attempt to send an e-mail to empty list of recipients, ignored. Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered

          Jan Vodolan added a comment -

          And another one ...
          [INFO] BUILD SUCCESS
          [INFO] ------------------------------------------------------------------------
          [INFO] Total time: 03:53 min
          [INFO] Finished at: 2017-05-15T09:36:18+02:00
          [INFO] Final Memory: 144M/880M
          [INFO] ------------------------------------------------------------------------
          channel stopped
          Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
          Finished: UNSTABLE

          Jan Vodolan added a comment - And another one ... [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 03:53 min [INFO] Finished at: 2017-05-15T09:36:18+02:00 [INFO] Final Memory: 144M/880M [INFO] ------------------------------------------------------------------------ channel stopped Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: UNSTABLE

          This happens quite often in builds of Apache Beam https://beam.apache.org/ - for example, https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/5313/ reports no failures, but is marked as unsuccessful. The respective build notification email also ends with "channel stopped":

           
          2017-11-27T12:54:54.110 [INFO] ------------------------------------------------------------------------
          2017-11-27T12:54:54.110 [INFO] BUILD SUCCESS
          2017-11-27T12:54:54.110 [INFO] ------------------------------------------------------------------------
          2017-11-27T12:54:54.110 [INFO] Total time: 53:22 min
          2017-11-27T12:54:54.111 [INFO] Finished at: 2017-11-27T12:54:54+00:00
          2017-11-27T12:54:55.019 [INFO] Final Memory: 410M/1593M
          2017-11-27T12:54:55.019 [INFO] ------------------------------------------------------------------------
          channel stopped
           
          I hope this link to a public build will help somebody get to the bottom of this, because the issue is quite annoying, and tests often have to be rerun for no reason except for this Jenkins bug. In case debugging this involves ssh'ing to executors - they are owned by ASF and I suppose, if needed, we can find a way to talk to people in charge of the infrastructure.

          Eugene Kirpichov added a comment - This happens quite often in builds of Apache Beam https://beam.apache.org/  - for example, https://builds.apache.org/job/beam_PostCommit_Java_MavenInstall/5313/  reports no failures, but is marked as unsuccessful. The respective build notification email also ends with "channel stopped":   2017-11-27T12:54:54.110 [INFO] ------------------------------------------------------------------------ 2017-11-27T12:54:54.110 [INFO] BUILD SUCCESS 2017-11-27T12:54:54.110 [INFO] ------------------------------------------------------------------------ 2017-11-27T12:54:54.110 [INFO] Total time: 53:22 min 2017-11-27T12:54:54.111 [INFO] Finished at: 2017-11-27T12:54:54+00:00 2017-11-27T12:54:55.019 [INFO] Final Memory: 410M/1593M 2017-11-27T12:54:55.019 [INFO] ------------------------------------------------------------------------ channel stopped   I hope this link to a public build will help somebody get to the bottom of this, because the issue is quite annoying, and tests often have to be rerun for no reason except for this Jenkins bug. In case debugging this involves ssh'ing to executors - they are owned by ASF and I suppose, if needed, we can find a way to talk to people in charge of the infrastructure.

          This is actually happening multiple times per day for us. Here's another example https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/4417/console

          Eugene Kirpichov added a comment - This is actually happening multiple times per day for us. Here's another example  https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow/4417/console

            kaosko kaosko
            mgrosz Maty Grosz
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: