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

ci: lock all kas repos #36

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Conversation

quaresmajose
Copy link
Contributor

@quaresmajose quaresmajose commented Oct 11, 2024

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

@quaresmajose quaresmajose requested review from ricardosalveti and a team October 11, 2024 12:03
.github/workflows/build-yocto.yml Outdated Show resolved Hide resolved
.github/workflows/build-yocto.yml Outdated Show resolved Hide resolved
@quaresmajose quaresmajose force-pushed the lock branch 3 times, most recently from 6110338 to e2a211a Compare October 11, 2024 16:48
@quaresmajose
Copy link
Contributor Author

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.

@quaresmajose quaresmajose self-assigned this Oct 11, 2024
@quaresmajose
Copy link
Contributor Author

Depends on #39

@ricardosalveti
Copy link
Contributor

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).

.github/workflows/build-yocto.yml Show resolved Hide resolved
.github/workflows/build-yocto.yml Outdated Show resolved Hide resolved
@quaresmajose
Copy link
Contributor Author

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

@quaresmajose quaresmajose force-pushed the lock branch 2 times, most recently from 0c4ed16 to 9a2eb54 Compare October 15, 2024 11:11
@quaresmajose
Copy link
Contributor Author

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]>
Copy link
Contributor

@ricardosalveti ricardosalveti left a comment

Choose a reason for hiding this comment

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

LGTM

@ricardosalveti ricardosalveti merged commit 6615b55 into qualcomm-linux:main Oct 15, 2024
7 checks passed
@quaresmajose quaresmajose deleted the lock branch October 15, 2024 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

KAS configuration file with stable commit for respective projects
3 participants