CircleCI Convenience Images => Clojure
A Continous Integration focused Clojure Docker image built to run on CircleCI
This image is in beta and is designed to supercede the original CircleCI Clojure image, circleci/clojure
.
cimg/clojure
is a Docker image created by CircleCI with continuous integration builds in mind.
Each tag contains a Clojure version, a JVM, and any binaries and tools that are required for builds to complete successfully in a CircleCI environment.
Table of Contents
Getting Started
This image can be used with the CircleCI docker
executor.
For example:
jobs:
build:
docker:
- image: cimg/clojure:1.10.1
steps:
- checkout
- run: lein version
In the above example, the CircleCI Clojure Docker image is used for the primary container.
More specifically, the tag 1.10.1
is used meaning the version of Clojure will be Clojure v1.110.1.
You can now use Clojure within the steps for this job.
How This Image Works
This image contains the Clojure programming language as installed via Leiningen. These Clojure images will contain OpenJDK v11.
Variants
This image will have a Node.js variant in the future.
Variant images typically contain the same base software, but with a few additional modifications.
The Node.js variant is the same Clojure image but with Node.js also installed.
The Node.js variant will be used by appending -node
to the end of an existing cimg/clojure
tag.
Tagging Scheme
This image has the following tagging scheme:
cimg/clojure:<clojure-version>[-variant]
<clojure-version>
- The version of Clojure to use.
This can be a full SemVer point release (such as 1.10.1
) or just the minor release (such as 1.10
).
If you use the minor release tag, it will automatically point to future patch updates as they are released by the Clojure Team.
For example, the tag 1.10
points to Clojure v1.10.1 now, but when the next release comes out, it will point to Clojure v1.10.2.
[-variant]
- Variant tags, if available, can optionally be used.
Once the Node.js variant is available, it could be used like this: cimg/clojure:1.10-node
.
Development
Images can be built and run locally with this repository. This has the following requirements:
- local machine of Linux (Ubuntu tested) or macOS
- modern version of Bash (v4+)
- modern version of Docker Engine (v19.03+)
Cloning For Community Users (no write access to this repository)
Fork this repository on GitHub.
When you get your clone URL, you'll want to add --recurse-submodules
to the clone command in order to populate the Git submodule contained in this repo.
It would look something like this:
git clone --recurse-submodules <my-clone-url>
If you missed this step and already cloned, you can just run git submodule update --recursive
to populate the submodule.
Then you can optionally add this repo as an upstream to your own:
git remote add upstream https://github.com/CircleCI-Public/cimg-clojure.git
Cloning For Maintainers ( you have write access to this repository)
Clone the project with the following command so that you populate the submodule:
git clone --recurse-submodules [email protected]:CircleCI-Public/cimg-clojure.git
Generating Dockerfiles
Dockerfiles can be generated for a specific Clojure version using the gen-dockerfiles.sh
script.
For example, to generate the Dockerfile for Clojure v1.10.1, you would run the following from the root of the repo:
./shared/gen-dockerfiles.sh 1.10.1
The generated Dockerfile will be located at ./1.10/Dockefile
.
To build this image locally and try it out, you can run the following:
cd 1.10
docker build -t test/clojure:1.10.1 .
docker run -it test/clojure:1.10.1 bash
Building the Dockerfiles
To build the Docker images locally as this repository does, you'll want to run the build-images.sh
script:
./build-images.sh
This would need to be run after generating the Dockerfiles first. When releasing proper images for CircleCI, this script is run from a CircleCI pipeline and not locally.
Publishing Official Images (for Maintainers only)
The individual scripts (above) can be used to create the correct files for an image, and then added to a new git branch, committed, etc. A release script is included to make this process easier. To make a proper release for this image, lets's use the fake Clojure version of Clojure v9.99, you would run the following from the repo root:
./shared/release.sh 9.99
This will automatically create a new Git branch, generate the Dockerfile(s), stage the changes, commit them, and push them to GitHub. All that would need to be done after that is:
- wait for build to pass on CircleCI
- review the PR
- merge the PR
The master branch build will then publish a release.
Incorporating Changes
How changes are incorporated into this image depends on where they come from.
build scripts - Changes within the ./shared
submodule happen in its own repository.
For those changes to affect this image, the submodule needs to be updated.
Typically like this:
cd shared
git pull
cd ..
git add shared
git commit -m "Updating submodule for foo."
parent image - By design, when changes happen to a parent image, they don't appear in existing Clojure images. This is to aid in "determinism" and prevent breaking customer builds. New Clojure images will automatically pick up the changes.
If you really want to publish changes from a parent image into the Clojure image, you have to build a specific image version as if it was a new image. This will create a new Dockerfile and once published, a new image.
Clojure specific changes - Editing the Dockerfile.template
file in this repo is how to modify the Clojure image specifically.
Don't forget that to see any of these changes locally, the gen-dockerfiles.sh
script will need to be run again (see above).
Contributing
We encourage issues to and pull requests against this repository however, in order to value your time, here are some things to consider:
- We won't include just anything in this image. In order for us to add a tool within the Clojure image, it has to be something that is maintained and useful to a large number of Clojure developers. Every tool added makes the image larger and slower for all users so being thorough on what goes in the image will benefit everyone.
- PRs are welcome. If you have a PR that will potentially take a large amount of time to make, it will be better to open an issue to discuss it first to make sure it's something worth investing the time in.
- Issues should be to report bugs or request additional/removal of tools in this image. For help with images, please visit CircleCI Discuss.
Additional Resources
CircleCI Docs - The official CircleCI Documentation website.
CircleCI Configuration Reference - From CircleCI Docs, the configuration reference page is one of the most useful pages we have.
It will list all of the keys and values supported in .circleci/config.yml
.
Docker Docs - For simple projects this won't be needed but if you want to dive deeper into learning Docker, this is a great resource.
License
This repository is licensed under the MIT license. The license can be found here.