- You have public repo on GitHub
- You ran at least one build on Travis
- You have Docker set up on your computer
Set up the build environment
Make up your own temporary build ID
Run the headless server
docker run --name $BUILDID -dit $INSTANCE /sbin/init
Run the attached client
docker exec -it $BUILDID bash -l
Run the job
Now you are now inside your Travis environment. Run
su - travis to begin.
This step is well defined but it is more tedious and manual. You will find every command that Travis runs in the environment. To do this, look for for everything in the right column which has a tag like 0.03s.
On the left side you will see the actual commands. Run those commands, in order.
Now is a good time to run the
history command. You can restart the process and replay those commands to run the same test against an updated code base.
- If your repo is private:
ssh-keygen -t rsa -b 4096 -C "YOUR EMAIL REGISTERED IN GITHUB"then
cat ~/.ssh/id_rsa.puband click here to add a key
- FYI: you can
git pullfrom inside docker to load commits from your dev box before you push them to GitHub
- If you want to change the commands Travis runs then it is YOUR responsibility to figure out how that translates back into a working
- I don't know how to clean up the Docker environment, it looks complicated, maybe this leaks memory