This repository is a combination of several tools which work in unison:
- Action: ci-storage. A GitHub action which uses ci-storage command-line tool.
- Command-line tool: ci-storage. The tool itself. It can be used stand-alone too.
- Docker image: ci-storage. Allows to launch ci-storage part of self-hosted runners infra.
- Docker image: ci-scaler. Scales runners based on GitHub's webhook signal using various heuristics.
- Docker image: ci-runner. Allows to launch self-hosted runners themselves.
This action quickly (only when run on your own self-hosted runners infra) stores the content of the work directory in the storage with the provided slot id on a remote host, or loads the content from the storage to that directory. The tool makes some smart differential optimizations along the way to operate as fast as possible (typically, 4 seconds for a 1.5G directory with 200K files in it on Linux EXT4).
Under the hood, the tool uses rsync. When storing to the remote storage, it uses rsync's "--link-dest" mode pointing to the most recently created slot, to reuse as many existing files in the storage as possible (hoping that almost all files to be stored in the current slot are the same as the files in the recent slot, which is often times true for e.g. node_modules directories). If a slot with the same id already exists, it is overwritten in a transaction-safe fashion.
When loading the files from a remote storage slot to a local directory, implies that the local directory already contains almost all files equal to the remote ones, so rsync can run efficiently.
Note
This tool makes sense only when using it with Self-Hosted Runners. The main idea is to reuse the previous build artifacts in work directories, which is not possible with default GitHub-Hosted Runners (GitHub always boots the virtual machines with empty work directories).
- uses: dimikot/ci-storage@v1
with:
# What to do (store or load).
# Required.
action: ''
# Storage host in the format [user@]host[:port]; it must allow password-free
# SSH key based access.
# Default: the content of ~/ci-storage-host file.
storage-host: ''
# Storage directory on the remote host. Notice that, when building the final
# directory on the storage host, owner and repo are always appended, so the
# path will be {storage-dir}/{owner}/{repo}/{slug(local-dir)} or
# {storage-dir}/{owner}/{repo}/{slug(local-dir)}.{layer-name}.
# Default: /mnt
storage-dir: ''
# Remove slots created earlier than this many seconds ago.
# Default: 14400 (4 hours).
storage-max-age-sec: ''
# Id of the slot to store to or load from; use "*" to load a smart-random
# slot (e.g. most recent or best in terms of layer compatibility) and skip
# if it does not exist.
# Default: $GITHUB_RUN_ID (which is friendly to "Re-run failed jobs").
slot-id: ''
# Local directory path to store from or load to. The value namespaces the
# data stored, so different local-dir values correspond to different
# storages. If the owner of the directory is different from the current
# user, then ci-storage tool is run with sudo, and the binary is used not
# from the action directory, but from /usr/bin/ci-storage.
# Default: "." (current work directory).
local-dir: ''
# Newline separated exclude pattern(s) for rsync.
# Default: empty.
exclude: ''
# If set, the final directory on the storage host will be
# {storage-dir}/{owner}/{repo}/{slug(local-dir)}.{layer-name},
# plus deletion will be turned off on load.
# Default: empty.
layer-name: ''
# Newline-separated include pattern(s) for rsync. If set, only the files
# matching the patterns will be transferred. Implies setting layer-name.
# Default: empty.
layer-include: ''
# If set, uses /usr/bin/ci-storage path and runs it with sudo. Useful for
# storing/loading privileged directories like Docker volumes.
# Default: false.
sudo: ''
# If set, runs the specified bash command before storing/loading.
# Default: empty.
run-before: ''
# If set, prints the list of transferred files.
# Default: false.
verbose: ''jobs:
build:
name: Build
runs-on: [self-hosted]
steps:
- name: Checkout
uses: actions/checkout@v4
- name: Build
run: npm i && npm run build
- name: Store build artifacts, work directory and .git directory
uses: dimikot/ci-storage@v1
with:
action: store
storage-host: my-hostname.com
test:
# ...
lint:
# ...The benefit in speed can only be achieved if you use self-hosted Action Runners. In this case, the content of work directory will be reused across the jobs runs, and ci-storage action will be very quick in loading the files and build artifacts (it will skip most of unchanged files).
jobs:
build:
# ...
test:
name: Test
needs: build
runs-on: [self-hosted]
steps:
- name: Load build artifacts, work directory and .git directory
uses: dimikot/ci-storage@v1
with:
action: load
storage-host: my-hostname.com
- name: Run tests
run: npm run test
lint:
# ...The command-line tool allows to run ci-storage manually.
A part of self-hosted runners infra representing the storage for ci-storage tool.
A part of self-hosted runners infra which dynamically launches more self-hosted runner spot instances when needed, recycles idle resources etc.
A part of self-hosted runners infra representing GitHub Actions runner.
The project and documentation are released under the MIT License.