ROCKs CI convention: single-rock repositories should include a subfolder for their rock

[orfeas-k]

The way ROCKs CI is designed right now implies that it doesn't work (as it should) for single-rock repository structure where the rockcraft.yaml file is placed in the repo's parent directory (example).

How ROCKs CI works

• Get all directories containing a rockcraft.yaml file
• Look for changes in that directory (including subdirectories)
• Trigger the build-scan-test ci if there are changes.

This means that it will trigger the workflow and rebuild the rock for changes to any file in the repo.

Solution

Since during discussions with the team, we agreed that we prefer single-rock repositories to include a subfolder for their rock (example), then we can:

1. Take this convention into consideration when creating spec for the CI Create a spec for ROCKs CI #48
2. Document that this is how it works explicitly Create documentation for reusable ROCKs CI #47
3. Restructure any rock repository not following the agreed structure.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5495.

This message was autogenerated