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:
Take this convention into consideration when creating spec for the CI #48
Document that this is how it works explicitly #47
Restructure any rock repository not following the agreed structure.
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
rockcraft.yaml
fileThis 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: