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

Trigger next gating using github action #637

Merged
merged 1 commit into from
Mar 10, 2025

Conversation

lsfreitas
Copy link
Contributor

This action will help preventing next-trigger for running every 15 minutes looking for changes. We'll trigger next gating directly on push for next* branches.

Fixes: #636

@lsfreitas lsfreitas self-assigned this Mar 5, 2025
@lsfreitas lsfreitas changed the title Trigger next gating using github action [DO NOT MERGE] - Trigger next gating using github action Mar 5, 2025
@yaronkaikov yaronkaikov requested a review from fruch March 5, 2025 08:25
@lsfreitas lsfreitas force-pushed the trigger-next-gating-action branch from eeab182 to af0cd59 Compare March 5, 2025 14:57
@lsfreitas lsfreitas requested a review from yaronkaikov March 5, 2025 16:49
Copy link
Contributor

@yaronkaikov yaronkaikov left a comment

Choose a reason for hiding this comment

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

@lsfreitas please remove [DO NOT MERGE]

@lsfreitas lsfreitas changed the title [DO NOT MERGE] - Trigger next gating using github action Trigger next gating using github action Mar 6, 2025
@lsfreitas
Copy link
Contributor Author

V2:

  • Use github action instead of curl
  • Successfully tested for scylla-machine-image

@fruch can you please review it?

@yaronkaikov
Copy link
Contributor

@scylladb/ccm-maint Can you please merge this?

@yaronkaikov yaronkaikov marked this pull request as draft March 9, 2025 14:15
@roydahan
Copy link
Contributor

roydahan commented Mar 9, 2025

Why is it a draft?

@yaronkaikov
Copy link
Contributor

@roydahan it should be fixed. tomorrow @lsfreitas will handle this

This action will help preventing next-trigger for running every 15 minutes looking for changes. We'll trigger next gating directly on push for next* branches.

Fixes: scylladb#636
@lsfreitas lsfreitas force-pushed the trigger-next-gating-action branch from 5636ddc to 292a8d4 Compare March 10, 2025 08:25
@lsfreitas lsfreitas marked this pull request as ready for review March 10, 2025 08:29
@lsfreitas
Copy link
Contributor Author

lsfreitas commented Mar 10, 2025

@yaronkaikov @Annamikhlin @fruch, this is ready for review

Copy link
Contributor

@fruch fruch left a comment

Choose a reason for hiding this comment

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

LGTM

@fruch fruch merged commit 5392dd6 into scylladb:next Mar 10, 2025
4 checks passed
@yaronkaikov
Copy link
Contributor

@fruch i thought this will not be relevant due to https://github.com/scylladb/scylla-pkg/pull/4954/

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.

Apply github action to start next-trigger jenkins jobs to run only when new changes are pushed
4 participants