John Niang

I'm wondering if we can run the `ks-jenkins` in GitHub workflow exactly after every build of `ks-jenkins`. This run may detect dependency problems.

If this issue was unresolved, our CI wouldn't be passed fully. Sorry for the bad news. ```bash kubespheredev/ks-jenkins:pr-78 (debian 11.2) ============================================ Total: 0 (HIGH: 0, CRITICAL: 0) Java (jar) ==========...

/kind support Thanks for reaching out here. There are several step you can try: - Describe the Pod `ks-jenkins` and check the exit code of Container `ks-jenkins` - Check latest...

I don't quite agree. Now it's time to test whether there is a problem with the upgraded Jenkins and the Jenkins plugins will cause conflicts with upgraded Jenkins.

> We can build an image from the master branch if we want to test it. Agree.

/kind feature-request

The earliest docker image supporting arm64 without suffix is in https://hub.docker.com/r/jenkins/jenkins/tags?page=1&ordering=last_updated&name=2.307.

May influenced by: https://github.com/jahudka/mdarea/blob/5369c6c2c0ce33bcc0f03420af693b509f2f2d8b/src/utils/dom.ts#L88

Hi @DarkWayne ，你可以试试根据下面的 AuthProvider 样例自己配置一个符合你的认证系统的 AuthProvider： ```diff apiVersion: auth.halo.run/v1alpha1 kind: AuthProvider metadata: + name: gitlab labels: auth.halo.run/auth-binding: "true" spec: + displayName: GitLab + description: GitLab Inc. is an open-core company...

接 ： Hi @DarkWayne ，还需要创建一个 Oauth2ClientRegistration 才行，示例如下： ```yaml apiVersion: oauth.halo.run/v1alpha1 kind: Oauth2ClientRegistration metadata: name: gitlab spec: clientAuthenticationMethod: "client_secret_basic" authorizationGrantType: "authorization_code" redirectUri: "{baseUrl}/login/oauth2/code/gitlab" scopes: - "read_user" authorizationUri: "https://gitlab.com/oauth/authorize" tokenUri: "https://gitlab.com/oauth/token" userInfoUri:...