🎯 Use Travis configuration to run stuff locally in a clean environment.
Your very own local way of testing!
Previs is using the travis configuration mechanism to provide your own local service of continuous integration. No more accidental error that trigger a fail build, no more plumbing on your git history. But more than a local travis, it provides you a way of testing in a sandboxed environment and more...
Previs is also providing a way to run things in a clean environment with no side effect thank's to Docker.
Previs is still in active development.
Previs is using docker at his heart, so of course you will need the docker daemon.
One of the simplest way to install it, it's by using the bash script:
$> curl -fsSL get.docker.com -o get-docker.sh $> sh get-docker.sh
If you are on Mac, it's here
You may have some trouble with permissions when attempting to run docker, if so, run the following command:
sudo usermod -a -G docker $USER
If the issue still persists, reboot your system.
Previs is snapped. He is using snapcraft which made very easy to install on linux system. The snapped software are updated automatically.
You have to run two commands and you will be ready to use Previs:
$> sudo apt install snapd
$> sudo snap install previs
As mentionned in !8, we let the possibility to still install the previous (0.4.1) version with the lighter image, so if you want the lighter image with less features:
$> sudo snap install --edge previs
$> sudo snap install --beta previs
For others package manager see.
Snap binary are located in
/snap/bin/, make sure it is integrated in your $PATH env.
If you run an other operating system or you don't want to install it via snap, you can still install it "manually" by installing Go first, then by doing:
$> go get -v github.com/PaulRosset/previs
Then make sure that your env variable $PATH contain the path where the go binary live.
Or you can still download the binary of release.
Previs is simple to use, he is using the travis mechanism to run 'things' in a clean environment.
However, since we are running things locally, we can't reproduce everythings that Travis is providing, so when the
.travis.yml get too complex, you have the possibility to switch on a custom file named
.previs.yml, then previs will take the configuration of the
Once you are at the root of your repository where the
.previs.yml is, you can launch:
$> previs [-p]
-p command indicate to previs to take the configuration of the
.previs.yml instead of the
Go find out how Previs work right now and know more what you can do before using it, by checking out our Wiki
Previs understand a failed build when the program ran is returning other than the 0 exit code.
Concerning the workflow of testing, rather than create unit tests on multiple call systems that already been tested especially docker calls, we instead run the program in real world use case to verify nothing broke and prevent regressions.
To understand it, you can check out the
.travis.yml file that serve th is purpose.
On the other hand, for the configuration parsing of Travis mechanism, we have a package travis that is only doing this purpose and where some tests resides.
Any contributions is very welcomed, let's do something bigger and stronger together!
Points that will be improved: