CI

[ivomarino]

We want to add continuous integration via Jenkins to the AppFlow development process. This means when we push to master or some else to-define branch we automatically:

• Create atlantis or atlantis.centos from scratch each time.
• Start a clean AppFlow provisioning for that new node.
• Send results via mail or notify in Slack.
• Destroy the created Vagrant VM.
• Restart the process.

all this via Jenkins which can run remotely or locally.

[ivomarino]

We've started using a solution based on Docker and Jenkins.

[sneaker]

Hi Ivo

I recently implemented this using gitlab. Everything based on docker. Maybe you want to have a look at it https://about.gitlab.com/gitlab-ci/ Gitlab also provides a git repository and a new issue tracking system. It can be hosted by yourself or use a free (for closed source development) version on gitlab.com. You really can feel that it is from one hand. It works much better than all this plugins from various sources on jenkins.

Maybe worth a look Best, Thomas

[ivomarino]

thanks @sneaker, sounds great I'll take a look. Since yesterday we're running Jenkins as a simple docker-compose process on OSX and Linux:

it's actually quite simple, Jenkins in Docker connects back to the dockerhost (bare metal notebook) via ssh destroys and recreates Vagrant boxes there in order to provision them from scratch each time, seems starting to work for now;)

[ivomarino]

we have a first complete AppFlow run via Jenkins on testing:

[ivomarino]

Introduced with https://github.com/ttssdev/appflow/commit/01f4cb6d90809dcfd37dc6958a30ac425f737c42 based on Docker, on OSX sudo ifconfig lo0 alias 10.200.10.1/24 ; source ~/.appflow/config ; docker stop jenkins ; docker-compose up then Jenkins will be on http://localhost:8080.