-
Notifications
You must be signed in to change notification settings - Fork 7.7k
ci(gitlab): Initial GitLab setup #11577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
👋 Hello lucasssvaz, we appreciate your contribution to this project! 📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more. 🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project. Click to see more instructions ...
Review and merge process you can expect ...
|
Memory usage test (comparing PR against master branch)The table below shows the summary of memory usage change (decrease - increase) in bytes and percentage for each target.
Click to expand the detailed deltas report [usage change in BYTES]
|
This pull request introduces enhancements to the GitLab CI/CD pipeline configuration by adding new workflow rules, default settings, and a sample job. These changes aim to improve pipeline behavior, provide default configurations, and include a simple example for demonstration purposes.
Workflow Rules Enhancements:
.gitlab-ci.yml
: Added rules to handle non-protected branches, merge request pipelines, and scheduled runs. Default settings are now included from external files.Default Pipeline Settings:
.gitlab/workflows/common.yml
: Defined default stages (pre_check
,build
,test
,result
), variables (ESP_IDF_VERSION
,ESP_ARDUINO_VERSION
), and retry policies for jobs.Example Job:
.gitlab/workflows/sample.yml
: Added a sample job (hello-world
) that echoes "Hello, World from GitLab CI!" as a simple demonstration.