jenkinsci / jenkinsci/github-branch-source-plugin

[JENKINS-64389] Multibranch GitHub Pipeline - Branches get wiped out randomly

Open
#1,329 2 comments 0 reactions 0 assignees View on GitHub
component:github-api-plugin component:github-branch-source-plugin imported-jira-issue priority:major resolution:unresolved
Dominant language
Java
Stars
217
Forks
398
Avg merge
30m
Merged PRs (30d)
1

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.

---
Originally reported by arixmf, imported from: Multibranch GitHub Pipeline - Branches get wiped out randomly


  • status: Open
  • priority: Major
  • component(s): github-api-plugin, github-branch-source-plugin
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 2025-12-02

Raw content of original issue

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.

  • environment: Jenkins 2.268

1 attachment

- [image-2020-12-08-09-38-58-224.png](https://issues.jenkins.io/secure/attachment/53530/image-2020-12-08-09-38-58-224.png)
> ![image-2020-12-08-09-38-58-224.png](https://issues.jenkins.io/secure/attachment/53530/image-2020-12-08-09-38-58-224.png)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.