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

ci: Improve workflow files #111

Merged
merged 15 commits into from
Oct 11, 2023
Merged

ci: Improve workflow files #111

merged 15 commits into from
Oct 11, 2023

Conversation

Techassi
Copy link
Member

@Techassi Techassi commented Sep 7, 2023

Tracked by #98

This PR reworks and streamlines GitHub Action workflow files. It tries to reduce runs by selecting which workflows to run based on file paths. It also limits on which events these workflows get triggered.

We currently (and will never) allow direct pushes to main. That's why it is sufficient to only run on pull_request for most of the workflows. Release workflows on the other hand get triggered by pushes (to main) with tags attached.

EDIT: We might want to re-add the merge_group trigger for workflow files which currently only use pull_request.

  • Migrate from actions-rs/clippy-check to giraffate/clippy-action
  • Integrate old jobs from Stackable Build Pipeline into new workflows

@Techassi Techassi self-assigned this Sep 7, 2023
@Techassi Techassi changed the title ci: Update workflow files ci: Improve workflow files Sep 20, 2023
Copy link
Member

@sbernauer sbernauer left a comment

Choose a reason for hiding this comment

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

Did you have the chance to test it e.g. in a fork?

.github/workflows/release_stackablectl.yml Show resolved Hide resolved
.github/workflows/release_stackablectl.yml Show resolved Hide resolved
@Techassi
Copy link
Member Author

Did you have the chance to test it e.g. in a fork?

No, but I can try it.

@@ -1,20 +1,16 @@
# =============
Copy link
Member

Choose a reason for hiding this comment

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

I assume the plan is to upstream this back into templating?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes. This is the ultimate goal. Depends how much we can re-use in the operator repos tho.

pull_request:
merge_group:
Copy link
Member

Choose a reason for hiding this comment

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

Definitely still want to run this for merge groups too?

Copy link
Member Author

Choose a reason for hiding this comment

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

If we check on every PR, we should not need it when merging as the code is tested and built beforehand. This ensures we don't push broken code into main.

.github/workflows/pr_cockpit-web.yml Show resolved Hide resolved
.github/workflows/pr_cockpit-web.yml Show resolved Hide resolved
Copy link
Member

@sbernauer sbernauer left a comment

Choose a reason for hiding this comment

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

I think we can start with this and improve it gradually if any problems arise

@Techassi Techassi added this pull request to the merge queue Oct 11, 2023
Merged via the queue into main with commit 36d8635 Oct 11, 2023
24 checks passed
@Techassi Techassi deleted the ci/rework branch October 11, 2023 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants