I have noticed this problem as well after updating to latest plugins this week.

stewartbryson camiloribeiro you have been effected by a bad SCM API upgrade that was rolled back from the update center. At the moment it isn't possible to cleanly rollback. We will be rolling out fixes in Blue Ocean when the SCM API has been fixed as part of JENKINS-40299.

I am really sorry for any inconvenience caused and rest assured we have a team of our best people working on it right now.

jamesdumay No worries thanks.

Thanks jamesdumay.

vivek I've assigned this one to you ask michaelneale said that you were managing most of the upgrade work for SCM 2.0 API. This ticket can be closed when we've got those changes on master.

hey stewartbryson can you try a "re-index" of jobs? (or did you already) as sometimes that is needed to update the metadata (at least for this release, I had to in some cases).

Didn't help fo me.

I believe we need to release a new version of Blue Ocean that is compatible with SCM 2.0 API. We are working on making that available right now but I don't have an ETA just yet.

jamesdumay Does uninstalling and reinstalling the plugin possibly help? I saw some chatter that it's because of an upgrade that we applied.

stewartbryson unfortunately that would make things worse For more context read the description on JENKINS-41234

I believe this is a duplicate (didn't catch it originally as thought it was limited to BlueOcean)

Are you saying the issue is fixed already?

stewartbryson Fix went in to scm-api/github-branch-source plugins. It's been fixed there and being tested in https://github.com/jenkinsci/blueocean-plugin/pull/742.

I know this issue was closed as a duplicate, but FYI the issue is resolved.

When JENKINS-41234 is resolved we consider this issue and all the related ones fixed and shipped.