Naoki Takezoe

GitBucket uses JGit's GitServlet to provude Git server functionality but it doesn't work with Servlet 5.0 yet. So we have no choice other than using Servlet 4.0 at this moment.

The default branch name will be configurable in GitBucket 4.40.0 but the default is still `master`. We will consider changing the default branch name to `main` in 4.41.0 or later.

OpenID Connect has been supported since GitBucket 4.21.0.

Closed as #2664 has been merged.

Is this everything you see? ``` SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details. 22:46:39.142 [main] INFO com.zaxxer.hikari.HikariDataSource -...

WARN message is not a problem. HikariCP just couldn't find a JDBC driver in the list of known JDBC drivers as GitBucket uses a custom JDBC driver. If GitBucket cannot...

So, could you elaborate your situation if you have still issues, or can we close this issue? Your meant that your GitBucket stopped working after that message?

Jetty 12 support has been merged in https://github.com/scalatra/scalatra/pull/1632

Do you mean that the build script configured by GitBucket admin is used in all repositopries?

> Although I think that the ci-plugin is not more insecure than some custom construction in Jenkins & Co. Yes, that's right. The purpose of that notice is calling attention...