-
Notifications
You must be signed in to change notification settings - Fork 26
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: lock all kas repos #36
Conversation
6110338
to
e2a211a
Compare
I think I will create another PR to refactor and merge the check-layer.yml in the build-yocto.yml since they are dependent on each other. |
Depends on #39 |
I think it is better if you can isolate just the lockfile related changes here, and do the rest in another pr (e.g. persistent dir, common root dir, etc). |
I removed the other stuff and will propose it in PR #41 |
0c4ed16
to
9a2eb54
Compare
I need to update the commit message since the implementation is already considerably different |
This guarantees that the build job can be easily replicated later. The kas will generate a file named base.lock.yml which will later be used instead of base.yml, we will save the lock file in action artifact in order to be shared with other jobs. Reference: https://kas.readthedocs.io/en/latest/userguide/project-configuration.html#working-with-lockfiles Signed-off-by: Jose Quaresma <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This guarantees that the build job can be easily replicated later.
The kas will generate a file named base.lock.yml which will later
be used instead of base.yml, we will save the lock file in action
artifact in order to be shared with other jobs.
Reference:
https://kas.readthedocs.io/en/latest/userguide/project-configuration.html#working-with-lockfiles
Fixes #21