One may often need to invoke the Travis CLI such as for encrypting environment variables for Travis CI, yet that requires to use travis's ruby binary, and hence requires a ruby runtime.
This small docker image exposes the travis CLI so that it is easily accessible and isolated inside of a docker container, leaving you out of the need to set it up yourself.
The docker image already has ruby and the travis gem installed so it can execute any
commands for the Travis CLI.
The image's entrypoint is set to the travis executable so any command line arguments
appended to docker run will be added to that, providing easy access to users.
docker run --rm -v ${HOME}/.travis:/root/.travis -it lirantal/travis-cli login
When encrypting something, the travis cli needs a way to know what travis repository
you are encrypting for so it can use the correct private key. This is either done by
being in the project's git repository which has the details, or providing a -r <owner>/<repo>
argument that specifies this.
This docker image uses the latter as a more verbose and flexible option to encrypt environment variables.
Example:
docker run --rm -v ${HOME}/.travis:/root/.travis lirantal/travis-cli encrypt ENV_VARIABLE_NAME="GH_TOKEN_GOES_HERE" -r lirantal/dockly
Or, to allow it to automatically detect the repository from the current directory:
docker run --rm -v ${HOME}/.travis:/root/.travis lirantal/travis-cli -v ${PWD}:${PWD} --workdir ${PWD} \
encrypt ENV_VARIABLE_NAME="GH_TOKEN_GOES_HERE" -r lirantal/dockly
Documentation Resources:
Add the lint command option and the path to the .travis.yml:
docker run --rm lirantal/travis-cli lint .travis.yml
You're welcome to suggest any changes and/or improvements by updating the Dockerfile or any other idea you may have.
Building the image from the Dockerfile and then you may execute it locally:
docker build --tag lirantal/travis-cli .
Liran Tal liran.tal@gmail.com