GitXplorerGitXplorer
k

cibox

public
5 stars
0 forks
1 issues

Commits

List of commits on branch master.
Unverified
5f28587de3ec8b4d6aa27864cde7ad2d24fd29e2

Base docker image on alpine

kkeis committed 9 years ago
Unverified
cfcd234be1f97dd5ba575b46973be7a59b5b94b0

remove extra print

kkeis committed 9 years ago
Unverified
0aead11f5758fb905b41614f5c299bed677b4f6e

fix execute test

kkeis committed 9 years ago
Unverified
7f40b76d90cc0b35ed79817b293c96e429ed06a2

Add a fancy spinner when pulling images

kkeis committed 9 years ago
Unverified
c30fe80d4720647af66734b026508713b8752637

send command output to logger

kkeis committed 9 years ago
Unverified
015cbca8a4c0031b9a67d66279d0539b05cb0cf1

capture stderr of subcommands

kkeis committed 9 years ago

README

The README file for this repository.

cibox

Build Status

A test runner for any language. It uses docker to create a container that will run the tests while keeping the control flow outside. This puts minimal restraints on the image as does not need do anything but run the normal commands for the target language.

cibox uses some travis idioms for convenience but full compatibility is not a goal.

Currently this is only a proof-of-concept and only supports a basic nodejs setup. Feedback is welcome (pull requests doubly so)

Setup

virtualenv --python python3.4 env
source env/bin/activate
pip install -r requirements.txt

Usage

build from a local directory

python ci.py /path/to/repo/

or from a git repository

python ci.py git+ssh://git@github.com/user/repo.git#branch

Tests

There is a few rudimentary tests written for cibox which of course can be run by cibox so that you can test that it can test and also run the tests

python ci.py "file:///$(pwd)"

Docker

It's not only using docker it can also be run using docker as long as you expose the docker socket into the container

docker run -ti -v /var/run/docker.sock:/var/run/docker.sock dkeis/cibox https://git@github.com/keis/cibox.git

Notes

http://docs.travis-ci.com/user/customizing-the-build/ https://github.com/docker/docker-py

  • parse yaml
  • start container of specified type
  • start executers in turn from the life cycle inside the container (defaults + configured)
  • before_install
  • install
  • before_script
  • script
  • after_success / afer_failure
  • after_script