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

Only build and publish new ROCK version if rockfile.yaml changed #16

Merged

Conversation

maci3jka
Copy link
Contributor

@maci3jka maci3jka commented Aug 5, 2024

No description provided.

@maci3jka
Copy link
Contributor Author

maci3jka commented Aug 5, 2024

@maci3jka maci3jka marked this pull request as ready for review August 5, 2024 14:18
@maci3jka maci3jka requested a review from bschimke95 August 7, 2024 09:07
Copy link

@bschimke95 bschimke95 left a comment

Choose a reason for hiding this comment

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

@maci3jka I'm not sure this will work like this.

If you only build the Rocks that have changed then the integration tests down the line will likely fail.

It is fine to build those ROCKs. Just don't publish them.

Looking at the linked test run they would still be published:
https://github.com/canonical/fluent-bit-rock/actions/runs/10278858107/job/28443209885?pr=9

.github/workflows/build_rocks.yaml Outdated Show resolved Hide resolved
.github/workflows/build_rocks.yaml Outdated Show resolved Hide resolved
@bschimke95 bschimke95 changed the title Story/ku 1195/build for changed rockfile Only build and publish new ROCK version if rockfile.yaml changed Aug 7, 2024
Copy link

@bschimke95 bschimke95 left a comment

Choose a reason for hiding this comment

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

LGTM

@bschimke95 bschimke95 merged commit 1d0eb45 into canonical:main Aug 7, 2024
7 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.

2 participants