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

Build status in GitHub is not updated properly when several builds run in parallel

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: github-api-plugin
    • Labels:
      None
    • Environment:
      jenkins:lts docker container (2.235.1) on Ubuntu 18.04.1 LTS, OpenJDK (1.8.0_242-b08)
    • Similar Issues:

      Description

      We have GitHub Organization plugin with declarative pipeline.

      Our pipeline looks for running builds of the same branch/PR and if any are detected, it kills other builds (if these are older than this one) or itself (if there are newer builds). It uses build number to determine which one is newer.

      If two builds are running in this way, and one of them is killed, the build status in GitHub does not update, and still points to the build that started first.

      This sometimes (but not always) is updated to the later build once that finishes.

      Could be related to JENKINS-62924, JENKINS-55726

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            eplodn1 efo plo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: