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

Logging of parallel pipeline job is not recording post stage after failed job

    XMLWordPrintable

Details

    Description

      The failure is sporadic (in more than 50% of the cases).

      The failure occures if the parallel jobs are executed and one of them failed. With the option failFast: true the complete pipeline jobs shall be aborted. The job is logging the jobs which were not yet started but already in the queue. At this point the logging stops.

      Normally I would expect in the logging:

      "
      Failed in branch XXX[Pipeline] }
      ...
      [Pipeline] // parallel[Pipeline] }[Pipeline] // scriptPost stage[Pipeline] script
      ..."

       

      But it stops with
      Failed in branch XXX[Pipeline] }
       

      Further mails which are initiated by the post stage are still sent. This gives the indication that the script is still running but the logging is stopped.

      Attachments

        Activity

          jenkins_supporter Martin Kadner added a comment -

          Any news on this ticket?

          jenkins_supporter Martin Kadner added a comment - Any news on this ticket?
          jenkins_supporter Martin Kadner added a comment -

          Who has an idea what the reason could be?

          jenkins_supporter Martin Kadner added a comment - Who has an idea what the reason could be?
          jenkins_supporter Martin Kadner added a comment -

          Logging stops with http error <Pipeline Job>/wfapi/changesets?_=1556858332241 ajax GET

          jenkins_supporter Martin Kadner added a comment - Logging stops with http error <Pipeline Job>/wfapi/changesets?_=1556858332241 ajax GET
          jenkins_supporter Martin Kadner added a comment -

          New finding: The log recording stop is depending on the load on the jenkins master. Increasing the hardware performance (more CPU power) stabilizes the logging.

          jenkins_supporter Martin Kadner added a comment - New finding: The log recording stop is depending on the load on the jenkins master. Increasing the hardware performance (more CPU power) stabilizes the logging.

          People

            Unassigned Unassigned
            jenkins_supporter Martin Kadner
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: