Skip to content

ci: in-line build-image workflow into pr #4480

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 1 commit into from
Jan 10, 2025

Conversation

erikgb
Copy link
Contributor

@erikgb erikgb commented Jan 10, 2025

Closes

What changed?

This inlines the build-image workflow into the PR workflow, making it a partial revert of #4468. Also trying to use similar settings as used when building release images. The workflow is mainly inlined to avoid triggering on Git tags. That could be fixed simpler by just modifying the on configuration, but I think it's cleaner to have it inside the PR workflow. After I realized there is a special image build in the release workflow.

Why was this change made?

When working on #4468, I didn't realize that there is a dedicated image build in the release workflow. We have decided to only make minor changes to the release process before cutting our first community releases.

How was this change implemented?

How did you validate the change?

Release notes

Documentation Changes

@erikgb erikgb requested a review from casibbald January 10, 2025 15:40
@erikgb erikgb enabled auto-merge January 10, 2025 15:40
@erikgb erikgb force-pushed the in-line-image-wf branch 3 times, most recently from 2401a59 to 914da8f Compare January 10, 2025 16:10
@erikgb erikgb disabled auto-merge January 10, 2025 16:15
@erikgb erikgb enabled auto-merge (rebase) January 10, 2025 16:15
@erikgb erikgb merged commit 4c57576 into weaveworks:main Jan 10, 2025
17 checks passed
This was referenced Jan 15, 2025
This was referenced Feb 4, 2025
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.

2 participants