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

Mark the job unstable when the Post-Build triggered job is not started

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Ubuntu 14.04 x86_64
      OpenJdk 7
      Jenkins 2.7.1
      Parameterized Trigger plugin 2.31
    • Similar Issues:

      Description

      Due to unreliable network environment,
      we'd randomly experience packet lost in network traffic.

      Hence,
      when an Upstream Jenkins job triggered a Downstream Jenkins job in Post-Build action,
      sometimes we found from Upstream Console Log that Upstream did trigger the job,

      Triggering a new build of $Downstream

      but Downstream job didn't start at all.

      We suspect it's that trigger package is lost on a way to Jenkins master.
      But I'd like the plugin to be able to handle this case,
      and mark the Upstream job as unstable or failure depends on the config
      instead of silently finished the job as successful.

        Attachments

          Activity

            People

            • Assignee:
              huybrechts huybrechts
              Reporter:
              totoroliu Rick Liu
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: