-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Update Dockerfiles and CI #1942
Conversation
instead of canary file
now that connext is fixed
I just saw the ROSCon lightning talk and wanted to have a look at the implementation. Great job digging through all the Docker docs and tutorials and distilling them into a thing like this ;) It's definitely an inspiration. I just wondered if I'm the only one who's lifting his eyebrows in front of the huge inefficiency of most Docker builds. I'm lucky I'm not alone =) I also used the I'm not sure if it's really needed, but at some point I added
I was also experimenting with Git caching, but one has to be careful there to not break when people force-push or do some other silly stuff. My first idea was to cache bare git repos and utilize them using something like |
It might be good for you to join our Slack group and talk to Ruffin or the rest of the team there ;-) |
Not another Slack group, please :-D But if you feel these ideas could be leveraged, feel free to open an issue in this repo and invite me in. Or maybe rather in some tooling repo? |
That looks new. What nuance effects does being explicit about the rewrite permissions to the cash volume have? By default, or when permissions are omitted, rewrite permissions are used, no? I may need to fix that then. |
Ah, my bad, rw is for bind mounts. cache mounts have ro instead (so I assume rw is the default). https://github.com/moby/buildkit/blob/master/frontend/dockerfile/docs/experimental.md#run---mounttypecache . When I was setting up our dockerfile, I had the impression that rw prevented some cache busts, but I can't tell for sure. |
* Use colcon to check for build failure instead of canary file * Simplify if case for shell * Move extra dockerfiles to docker related folder * Update Dockerfile location * Stage refactor * Use build kit * Update underlay and overlay build * Dockerfile tweek * Rename underlay .repos file * Remove uneeded key * Clone matching distro branch by default * Add optional directive to RUN colcon test * Add comments * Skip the use of symlinks * Roll back to nightly image with all rmws now that connext is fixed * Add slam_toolbox to skipped rosdep keys * Set DEBIAN_FRONTEND env to noninteractive * Update to tag foxy * Updated to latest codecov orb
Spinning out non-dumenten related CI changes from #1731 into own seperate PR.