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

Multibranch GitHub Pipeline - Branches get wiped out randomly

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I maintain a multibranch GitHub pipeline.

      There is a weird problem that occurs pretty rarely, but had already occurred enough times to become an inconvenience for us.

      At certain times, a certain branch/multiple branches/all branches in the pipeline would get wiped out, meaning, they would appear as though they were just discovered and all of the job history would get removed.

      This is pretty inconvenient because 

      1. we need past job history
      2. the build number gets reset, so I have manually set it to that of the latest build, otherwise, the build would fail because of version number conflict.

      My intuition is that it could be a momentary problem with GitHub that causes it to return partial information and the GitHub plugin doesn't handle it properly, but I don't have any evidence to support that.

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          I've removed the git plugin from the components and removed myself as the assigned person because you said that this is a GitHub multibranch pipeline. I assume that means you are using the GitHub multibranch provider (a very good choice) rather than the git multibranch provider (a poor choice when connected to a GitHub repository). If you are using the git multibranch provider to work with GitHub branches, then you should try the GitHub multibranch provider instead.

          I've never seen the problem that you describe in my environment. I use a wide range of GitHub multibranch pipelines and git multibranch pipelines.

          Show
          markewaite Mark Waite added a comment - I've removed the git plugin from the components and removed myself as the assigned person because you said that this is a GitHub multibranch pipeline. I assume that means you are using the GitHub multibranch provider (a very good choice) rather than the git multibranch provider (a poor choice when connected to a GitHub repository). If you are using the git multibranch provider to work with GitHub branches, then you should try the GitHub multibranch provider instead. I've never seen the problem that you describe in my environment. I use a wide range of GitHub multibranch pipelines and git multibranch pipelines.
          Hide
          arixmf Arik Lekar added a comment -

           

          I think I use the GitHub one instead of Git, based on what's in the screenshot (not sure 100%)

          Show
          arixmf Arik Lekar added a comment -   I think I use the GitHub one instead of Git, based on what's in the screenshot (not sure 100%)

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            arixmf Arik Lekar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: