Branch disabled in multibranch pipeline and reopened with Scan event
Asked Answered
I

3

6

We have one project configured as multibranch pipeline project with branch filtered master and development. After few hours the master branch is disabled with a strikethrough symbol across its name and build option not available .

When clicked on "Scan Multibranch Pipeline", it enabled the branch and pipeline logs show "Branch ReOpened".

Initially we assumed it would be because of Option "Exclude branches included in pull request" but enabling "All branches" too is disabling the master branch time and time again.

Pipeline Logs are not providing any clear indication of whats happening causing it to disable .Please help .

Impudence answered 2/11, 2020 at 12:35 Comment(0)
E
1

This looks like a bug to me. First I'll go to http://[jenkins]/log/all to see if there are any interesting logs there, then I would open an issue on https://issues.jenkins.io/secure/Dashboard.jspa

Also this issue might be happening after a recent upgrade of jenkins plugins or jenkins itself, I would downgrade everything to try to get my jenkins back to the way it was, then upgrade the plugins one by one or few by few to try to isolate what is causing the issue.

Finally, if you have jobdsl scripts, I would check these scripts to see if there is not a script that when executed is recreating the job and overrides the disabled status

Expulsion answered 11/11, 2020 at 11:29 Comment(1)
@alim-azad Were you able to fix the issue? Can you share the details?Khalil
P
6

Old topic but I faced the same error today but the solution was different.

The error was in the configuration of branch discovery Discover branches > Strategy. I was using Exclude branches that are also filed as PRs

And there was a PR targeting this branch. Change for All branches did the trick.

Percheron answered 11/11, 2022 at 2:31 Comment(1)
I wonder what's the sense in that option?Bathypelagic
E
1

This looks like a bug to me. First I'll go to http://[jenkins]/log/all to see if there are any interesting logs there, then I would open an issue on https://issues.jenkins.io/secure/Dashboard.jspa

Also this issue might be happening after a recent upgrade of jenkins plugins or jenkins itself, I would downgrade everything to try to get my jenkins back to the way it was, then upgrade the plugins one by one or few by few to try to isolate what is causing the issue.

Finally, if you have jobdsl scripts, I would check these scripts to see if there is not a script that when executed is recreating the job and overrides the disabled status

Expulsion answered 11/11, 2020 at 11:29 Comment(1)
@alim-azad Were you able to fix the issue? Can you share the details?Khalil
S
1

Not sure if you're using Bitbucket Branch Source plugin for hook on Jenkins, but I had the same issue on 737.vdf9dc06105be version. Everytime I pushed a change to branch (not pull request) it got disabled (strikethrough). Scan multibranch pipeline was restoring it until next push notification on webhook was performed. Upgrading the plugin to 751.vda_24678a_f781 version resolved the issues:)

Sims answered 24/2, 2022 at 11:0 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.