Migrate ci gitlab to GitHub #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change ensures that the build jobs for both the main build and the Build Rapport PDF depend on the successful execution of the check-envvars job, improving the CI/CD pipeline's reliability.
Eliminated the Maven settings setup step from the GitHub Actions CI pipeline as it is no longer necessary for the build process.
…iv repository since the connection seems to fail from the github actions servers.
Modified the CI configuration to install the CLI module alongside the LexerParser module during the build process. This change ensures that both modules are available for subsequent steps in the pipeline.
This change introduces a new packaging step in the CI pipeline to build and upload JAR artifacts. The step includes caching Maven packages and is conditioned to run on pull requests, tags, and specific branches.
This change introduces a step to install Git in the CI pipeline, ensuring that the necessary tools are available for subsequent steps during the build process.
Added qodana.yaml and qodana_code_quality.yml to configure Qodana for code analysis and quality checks in the CI/CD pipeline. This setup includes inspection profiles, severity thresholds, and job definitions for running Qodana scans on pull requests and pushes.
This change introduces a concurrency group to the CI pipeline, allowing for cancellation of in-progress jobs when new ones are triggered. This helps to optimize resource usage and improve build efficiency.
Modified the conditions under which the CI job runs to include specific checks for push events on the main and dev branches, as well as pull requests labeled with 'rapport'.
Qodana for JVM11 new problems were found
☁️ View the detailed Qodana report Contact Qodana teamContact us at qodana-support@jetbrains.com
|
Added steps to download test artifacts and GUI test artifacts in the CI pipeline to ensure that test results are accessible for further analysis.
Removed the separate check for environment variables from the 'check-envvars' job and integrated it into the 'build' job. This change simplifies the CI pipeline by reducing the number of jobs while ensuring that required secrets are still validated during the build process.
Modified the build command for the 'Rapport' module to utilize the MAVEN_CLI_OPTS environment variable, allowing for more flexible Maven command-line configurations.
Changed the reference from secrets to environment variables for SONAR_HOST_URL in the CI configuration to ensure proper access to the required SonarQube secrets during the CI process.
Changed the SONAR_HOST_URL reference in the CI configuration to utilize the environment variable instead of the secrets directly. This improves consistency and allows for easier management of environment-specific configurations.
Eliminated the step that checks for required SonarQube secrets in the CI configuration. This streamlines the process and assumes that the necessary environment variables and secrets are correctly set up elsewhere.
- Renamed the job from "Package" to "Package & Quality Analysis". - Updated job dependencies to include "build". - Added steps to download test artifacts. - Removed the SonarQube analysis job to streamline the CI process.
Modified the SonarQube cache key in the CI workflow to incorporate the branch name, allowing for better cache management and differentiation between branches. This change enhances the caching mechanism by ensuring that the cache is specific to the branch being built.
Removed the hash of the pom.xml file from the SonarQube cache key to streamline the caching process. The restore keys have also been simplified for better cache management.
Removed the hash of the pom.xml files from the SonarQube cache key to streamline the caching process and reduce complexity in the CI workflow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request migrates the project's CI/CD pipeline from GitLab CI to GitHub Actions. The
.gitlab-ci.ymlfile is removed, and a new.github/workflows/ci.ymlworkflow is introduced to handle all build, test, package, deployment, and analysis tasks. This transition ensures that all CI/CD processes are now managed via GitHub Actions, aligning with GitHub-hosted repositories and workflows.Key changes in this migration:
CI/CD Platform Migration:
.gitlab-ci.ymlfile, including all GitLab-specific stages, jobs, and configuration..github/workflows/ci.ymlfile defining the full CI/CD pipeline using GitHub Actions, covering build, test, SonarQube analysis, packaging, and deployment.Pipeline Structure and Features:
Container and Environment Consistency:
maven:3.9.9-eclipse-temurin-21-alpinefor Java/Maven tasks, and a custom image for LaTeX/PDF builds), mirroring the previous GitLab setup.Secrets and Security:
secretscontext, updating all references accordingly.This migration centralizes and modernizes the CI/CD process, making it compatible with GitHub repositories and leveraging GitHub Actions' native features.