jenkinsci / jenkinsci/gitlab-branch-source-plugin

[JENKINS-69052] Builds Getting Disabled even though branches exists and only geting enable on "GitLab scan Run"

Open
#710 0 comments 0 reactions 0 assignees View on GitHub
component:gitlab-branch-source-plugin imported-jira-issue priority:critical resolution:unresolved
Dominant language
Java
Stars
134
Forks
113
PR merge metrics
No merged PRs in 30d

Description

hello,



  • we are currently using jenkins to build new  builds of application based on the code changes regularly and we have observed that master/release builds getting disabled frequently even though we are not deleting the branches/disabling the jobs.

  • As alternate way we are currently using " scan gitlab now "which would scan all existing branches on particular pipeline which is not at all ideal way, to do so as it triggers all builds under this pipeline. to enable our required branch 

  • so please guide me to fix this issue on my jenkins if any plugins or required or troubleshooting required !! i was using below jenkins version Jenkins 2.303.3

 please reach out to me if you have any questions on ravi.pothula@​cerence.com

---
Originally reported by ravi_pothula, imported from: Builds Getting Disabled even though branches exists and only geting enable on "GitLab scan Run"


  • status: Open
  • priority: Critical
  • component(s): gitlab-branch-source-plugin
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 20251216-182730

Raw content of original issue

hello,



  • we are currently using jenkins to build new  builds of application based on the code changes regularly and we have observed that master/release builds getting disabled frequently even though we are not deleting the branches/disabling the jobs.

  • As alternate way we are currently using " scan gitlab now "which would scan all existing branches on particular pipeline which is not at all ideal way, to do so as it triggers all builds under this pipeline. to enable our required branch 

  • so please guide me to fix this issue on my jenkins if any plugins or required or troubleshooting required !! i was using below jenkins version Jenkins 2.303.3

 please reach out to me if you have any questions on ravi.pothula@cerence.com

1 attachment

- [jenkinsissue.PNG](https://issues.jenkins.io/secure/attachment/58514/jenkinsissue.PNG)
> ![jenkinsissue.PNG](https://issues.jenkins.io/secure/attachment/58514/jenkinsissue.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.