Skip to content

ci: Improving trigger jobs coverage #3408

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

Merged
merged 10 commits into from
Apr 16, 2025
Merged

ci: Improving trigger jobs coverage #3408

merged 10 commits into from
Apr 16, 2025

Conversation

michalChrobot
Copy link
Collaborator

@michalChrobot michalChrobot commented Apr 16, 2025

This PR aims to fix an oversight of having invalid dependency in Nightly trigger as well as adding more variations to PR trigger job.

Additionally it introduces run_quick_checks job that was added as a requirement for package_pack and project_pack jobs. It will run as a first check (also on PR trigger) to catch any basic errors (PVP and project standards) and ONLY IF this job will pass, the rest of PR trigger job dependencies will be executed.
This way provides faster feedback loop for developers and allow to minimize resource usage when unnecessary

Failing result may look like this
image
Where we can see that many jobs failed but in reality we can see that only PVP jobs failed and others were never executed and failed due to their dependencies

Backport

This is specific change to develop branch but it's somewhat reflected in #3409

@michalChrobot michalChrobot self-assigned this Apr 16, 2025
@michalChrobot michalChrobot marked this pull request as ready for review April 16, 2025 13:09
michalChrobot added a commit that referenced this pull request Apr 16, 2025
…ger jobs coverage (#3409)

This PR aims to add minimal supported editor (6000.0) specific tests so
we can differentiate between those and trunk tests as well as adding
more variations to PR trigger job.

Additionally it introduces _**run_quick_checks**_ job that was added as
a requirement for package_pack and project_pack jobs. It will run as a
first check (also on PR trigger) to catch any basic errors (PVP and
project standards) and ONLY IF this job will pass, the rest of PR
trigger job dependencies will be executed.
This way provides faster feedback loop for developers and allow to
minimize resource usage when unnecessary

Failing result may look like this

![image](https://github.com/user-attachments/assets/bc89acc7-1fad-4330-92df-407bef45c308)
Where we can see that many jobs failed but in reality we can see that
only PVP jobs failed and others were never executed and failed due to
their dependencies

## Backport
This is specific change to develop-2.0.0 branch but it's somewhat
reflected in
#3408
@michalChrobot michalChrobot merged commit 90c00cd into develop Apr 16, 2025
42 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant