Skip to content
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

.github/workflows: trigger gitlab as soon as possible #3553

Closed

Conversation

ondrejbudai
Copy link
Member

Previously, we gated the GitLab tests on the unit tests. However, these now take ~10 minutes, which is just annoying for engineers. This commit changes the trigger to fire immediately after the PR is updated. This should save our engineers 10 minutes on every push.

Regarding higher infra costs: Engineers are more expensive. :P

Previously, we gated the GitLab tests on the unit tests. However, these now
take ~10 minutes, which is just annoying for engineers. This commit changes
the trigger to fire immediately after the PR is updated. This should save our
engineers 10 minutes on every push.

Regarding higher infra costs: Engineers are more expensive. :P

Signed-off-by: Ondřej Budai <[email protected]>
Copy link
Member

@achilleas-k achilleas-k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

brrrrrr

@achilleas-k
Copy link
Member

Something wrong with the workflow now that it's a separate file?

@github-actions
Copy link

github-actions bot commented Sep 8, 2023

This PR is stale because it has been open 30 days with no activity. Remove "Stale" label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Sep 8, 2023
@github-actions
Copy link

This PR was closed because it has been stalled for 30+7 days with no activity.

@github-actions github-actions bot closed this Sep 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants