Disabeled branch on Multibranch pipeline project can not be enabled again

Using Jenkins Ask a question
,
1

Hello team,
all of the sudden Jenkins disabled one branch of my multibranch pipeline project (controller branch).
in the project page it is striked through like this screenshot:
image
and

image
image567×151 4.13 KB

nothing changed that I recall, Jenkins still detect PRs agains that branch and do the needed for PRs, but does not build this controller branch when something change or allow you to manually build the branch.
it says this project is currently disabled, the enable/disable button on the configuration page of this branch is grayed out and not funcional.

image
image1288×453 20.8 KB

I have couple branches on this poroject that are working nicely and another mutiple branch project that also working with no issues.
Multibranch Pipeline Events logs does not show any problem, I tried to run a newer scan and it detected controller but did not say the magic word ‘Met criteria’ nor jenkinsfile found
like this:

Checking branches...
Getting remote branches...
Checking branch [master](https://github.com/xxxxx)
     Getting remote pull requests... 
Checking branch [Current-CA](https://github.com/yyyyyyy) 
         ‘.ci/Jenkinsfile’ found
 Met criteria

my Jenkins is running inside a container with the version: 2.462.3

any hint on how can I get my branch to work normaly is appreciated

best regards,
Zuhir

2

Please make sure that the branch source configuration is correct and that the branch is not excluded by any filters.

3

anything specific to look at?
I did verify that multiple times, I have other multibranch pipeline projects that are working just fine,
my last try probably is to delete the whole branch and maybe start over.

image
image993×719 53.6 KB

that will be painful as I will lose my history of builds with no guarantee that this will be a fix.
I am more thinking that this is a kind of bug that disabled this build and no way to bring it bag, why would disable/enable button not functional?
image
image539×209 2.37 KB

4

Save the data from /var/lib/jenkins/jobs/your_jobname to some NFS location or somewhere where you can retrieve later. That way you won’t lose data.

For troubleshooting did you check with something changed in the github side? If the branch got deleted? webhook got changed?
Since you said disable/enable button greyed out. Can you ask someone with Admin privileges be able to toggle between disable/enable a job?

Did your Jenkinsfile exists in the correct path within the branch. If your project is looking for a Jenkinsfile in a specific directory (e.g., not in the root), Jenkins may skip it if it’s not where expected.

5

I am the admin in both Jenkins and GitHub, and as I said above, nothing changed that I am aware of,
anyway after I created a parallel job to allow team to use it while I am trying to figure out why this one is disabled, and on next day just found my old job back in normal state, I wish I can tell how did that happen but I don’t know.
thank you all for helping :slight_smile: