lazy-build

Cache build artifacts based on files on disk.

Interface

Building

$ lazy-build build \
    context= requirements*.txt setup.py /etc/lsb_release \
    output= venv \
    after-download= venv/bin/python -m virtualenv_tools --update-path {pwd}/venv venv \
    command= bash -euxc 'virtualenv -ppython3 venv && venv/bin/pip install -r requirements.txt'

Invalidating artifacts

lazy-build invalidate takes all of the same arguments as lazy-build build. It builds up the context, then deletes the artifact matching it.

$ lazy-build invalidate \
    context= requirements*.txt setup.py /etc/lsb_release \
    output= venv \
    after-download= venv/bin/python -m virtualenv_tools --update-path {pwd}/venv venv \
    command= bash -euxc 'virtualenv -ppython3 venv && venv/bin/pip install -r requirements.txt'

Ideally it would have an option to mark that the artifact should not be used/re-uploaded again, in cases where something might be broken with the generated artifacts. This could be used as an off-switch until fixes can be made.

The config file

Located as .lazy-build.json at the root of your project.

{
    "cache": {
        "source": "s3",
        "bucket": "my-cool-bucket",
        "path": "cache/my-cool-service"
    },
    "ignore": [
        "*.py[co]",
        "*~",
        ".*.sw*",
        ".DS_Store",
        ".nfs*"
    ]
}

Contributing

To start, run make minimal to set up a development virtualenv, then activate it with . venv/bin/activate. This will put a lazy-build executable on your path using the local version of the code.

There's an example project inside testing/example-project which contains a simple build script and Makefile. It uses a filesystem cache under a cache directory which you can easily inspect and clear during your testing. To attempt a build, run make thing. You should observe that the first run isn't cached, but the second is.