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

Add myfile #5

Draft
wants to merge 86 commits into
base: main
Choose a base branch
from
Draft

Add myfile #5

wants to merge 86 commits into from

Conversation

HeroCC
Copy link
Owner

@HeroCC HeroCC commented Apr 4, 2025

No description provided.

HeroCC added 30 commits October 1, 2024 22:45
Mostly taken from my extend tree
Remove the `--release` flag. This will make binaries a bit larger and slower, but is generally how most people build moos anyway.

This should also keep us from rebuilding the same libraries multiple times.
Split images are making tings difficult to debug. Let's get things working, and move back to parallelization if needed.
This reverts commit 1918951.

It takes too long.

https://docs.docker.com/build/ci/github-actions/multi-platform/#distribute-build-across-multiple-runners
is better, but not great -- too hacky, and relies on undocumented
functionality.

I'll make something better.
The gui layer is not respecting the already-built minrobot libraries. Probably because we install a bunch of new libraries.

Since we're not using the cache anyway, split the layers explicitly.
Utilize maximum caching, since this changes rarely
Simplify things more (until arch native runners come around)
Maybe this is cache busting?
May be slower, but is more understandable and less complex
Doesn't actually save us much time. Reduce some complexity.
SOURCE_DATE_EPOCH is used by GCC and other utilities to attempt to generate reproducable artifacts.
HeroCC added 29 commits October 24, 2024 23:30
Want to confirm our $FROM is being honored
Silly me :)
Not sure if Github will accept matrix builds like this
We don't necessarily publish
Run in the fork's namespace, not the upstream.
We only publish images on `main` and on forks.
Symlinked to `.gitignore`.

I've been using this pattern in my extend tree for successfully to prevent undesired artifacts from making their way into the docker image.
Much of the `baserobot` binaries are rebuilt after we install new libraries, so we're not benefitting from the shared cache.

This also simplifies the build process, and doesn't push (only builds) intermediate images unless we plan to publish them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant