ci: move jenkins operations to GH

[moabu]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #10081

Implementation Details

Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with docs: to indicate documentation changes or if the below checklist is not selected.

• I confirm that there is no impact on the docs due to the code changes in this PR.

[dryrunsecurity]

DryRun Security Summary

The pull request includes a wide range of updates to the Janssen Project's GitHub Actions workflows, build configurations, and documentation-related processes, focusing on improving the security, reliability, and maintainability of the project's codebase and build infrastructure.

Expand for full summary

Summary:

The code changes in this pull request cover a wide range of updates to the Janssen Project's GitHub Actions workflows, build configurations, and documentation-related processes. The changes focus on improving the security, reliability, and maintainability of the project's codebase and build infrastructure.

Key security-related updates include:

1. Hardening the GitHub Actions runners using the step-security/harden-runner action, which helps mitigate potential security risks.
2. Implementing Markdown linting to ensure the quality and consistency of the project's documentation.
3. Expanding the CodeQL static code analysis to include the Go programming language, which is a new addition to the project.
4. Securing the storage and management of sensitive credentials, such as GitHub access tokens and GPG keys, using GitHub Secrets.
5. Enhancing the testing capabilities by adding support for running tests for the SCIM server and Config API components of the Janssen platform.

Additionally, the changes introduce new Maven repository configurations, which should be carefully reviewed to ensure the security and integrity of the project's dependencies.

Files Changed:

1. .github/workflows/lint-docs.yml: This workflow is responsible for linting the Markdown files in the docs/ directory of the project. The changes focus on hardening the GitHub Actions runner and implementing Markdown linting to maintain the quality of the project's documentation.

2. .github/maven-settings.xml: This file updates the Maven configuration to use a GitHub Packages repository for the project's dependencies. The changes introduce the use of environment variables to store sensitive credentials, which should be properly secured.

3. .github/workflows/ops-docs.yml: This workflow manages the documentation-related changes in the project, including commit message checking, pull request verification, and Markdown linting. The changes help ensure the integrity and quality of the project's documentation.

4. .github/workflows/build-test.yml: This workflow is responsible for building and testing the Janssen Project. The changes include hardening the GitHub Actions runner, importing a GPG key for signing commits, and enabling dependency checking to identify known vulnerabilities.

5. .github/workflows/scan-codeql.yml: This workflow runs the CodeQL static code analysis tool on the project's codebase. The changes expand the language support to include the Go programming language, which is a positive step towards improving the overall security of the project.

6. Various other files, such as pom.xml and entrypoint.sh, which include updates to the project's build configurations and testing scripts. These changes should be reviewed to ensure they do not introduce any unintended security risks.

Code Analysis

We ran 9 analyzers against 30 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	4 findings

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[sonarqubecloud]

Quality Gate passed for 'agama parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed for 'jans-core'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed for 'keycloak-integration-parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed for 'jans-cli'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'Jans-Keycloak-Link'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'Fido2 API'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'jans-config-api-parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'SCIM API'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'jans-pycloudlib'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'jans-linux-setup'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud