Sha256: 4a78685110532693fc8eaadac64f94dd4adb9311974fed55cbee76fba5ffd9f8
Contents?: true
Size: 1.38 KB
Versions: 1
Compression:
Stored size: 1.38 KB
Contents
# Contributing This document is intended for the rake-compiler-dock contributors. ## Cutting a release - prep - [ ] make sure CI is green! - [x] update `History.md` and `lib/rake_compiler_dock/version.rb` - build - [x] run the steps below to generate the images locally - [x] run `gem build rake-compiler-dock` - [x] create a git tag - push - [x] run `bundle exec rake release:images` - [ ] run `gem push pkg/rake-compiler-dock*gem` - [ ] run `git push && git push --tags` - announce - [ ] create a release at https://github.com/rake-compiler/rake-compiler-dock/releases ## Building a versioned image We want to preserve the cache if we can, so patch releases don't change _all_ the layers. There are a few ways to do this. ### Using local docker If you're going to keep your local docker cache, around, you can run things in parallel: ``` bundle exec rake build ``` ### Use a custom docker command If you're a pro and want to run a custom command and still run things in parallel: ``` export RCD_DOCKER_BUILD="docker build --arg1 --arg2" bundle exec rake build ``` ### Using the buildx backend and cache Here's one way to leverage the buildx cache, which will turn off parallel builds but generates an external cache directory that can be saved and re-used: ``` export RCD_USE_BUILDX_CACHE=t docker buildx create --use --driver=docker-container bundle exec rake build ```
Version data entries
1 entries across 1 versions & 1 rubygems
Version | Path |
---|---|
rake-compiler-dock-1.4.0 | CONTRIBUTING.md |