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: Update KAS mirrors #82

Open
ndechesne opened this issue Nov 21, 2024 · 2 comments
Open

CI: Update KAS mirrors #82

ndechesne opened this issue Nov 21, 2024 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@ndechesne
Copy link
Contributor

We added support for KAS mirrors in f916c17, and thought that the mirrors would be updated with new objects (when using the --update command). As it happens this is not correct. KAS will effectively create the mirror repo when/if it does not exist, however it will never update the mirrors.

When running a checkout command with --update, KAS will first clone the repo from the mirror (which contains the git objects from the time the mirror was created), and then it fetches new objects from the remote repo. However the new objects are fetched in the kas workspace, but not in the mirror. Next time we run checkout with --update again, the same new objects are fetched again.

At first, I thought it was a bug, but it happens to be done 'by design' as discussed on the kas mailing list here:
https://groups.google.com/g/kas-devel/c/-TtiBdDlhJ0

We probably want to update the kas mirrors regardless, e.g. running git fetch command from time to time. That's what meta-arm is doing at https://git.yoctoproject.org/meta-arm/tree/ci/update-repos.

@quaresmajose
Copy link
Contributor

We probably want to update the kas mirrors regardless, e.g. running git fetch command from time to time. That's what meta-arm is doing at https://git.yoctoproject.org/meta-arm/tree/ci/update-repos.

I think we can do this daily in the nightly build.

@ricardosalveti
Copy link
Contributor

Running as we start the runs would also be ok from my perspective, since the job will have to fetch the missing object anyway.

@ricardosalveti ricardosalveti added this to the 12/24 milestone Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

No branches or pull requests

3 participants