You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to be able to test latest AppFlow code based on Continuous Integration via Jenkins.
The basic idea is to run Jenkins inside a Docker container or a FreeBSD Jail and trigger the build/test process on each git commit to master or a specific testing branch via pipeline.
The stages of the pipeline process (thanks to @sneaker for suggestions on this), should run in parallel and perform this specific tasks:
this allows self-provisioning agains mrrobot using local connection: root@ubuntu:/tmp/appflow# ansible-playbook -e conf_env=development --skip-tags hosts --limit local -i examples/appflow-mrrobot/development/inventory playbooks/generic.yml -- works inside a Docker container.
This also works in case we want to simulate atlantis:
We want to be able to test latest AppFlow code based on Continuous Integration via Jenkins.
The basic idea is to run Jenkins inside a Docker container or a FreeBSD Jail and trigger the build/test process on each
git commit
tomaster
or a specifictesting
branch viapipeline
.The stages of the pipeline process (thanks to @sneaker for suggestions on this), should run in parallel and perform this specific tasks:
ssh
, against the latestmrrobot
example configs.We should trigger the LXC/VM creation via API, like
pvesh
on Proxmox andvm
on FreeNAS Corral, we also could usecurl
REST API calls.The text was updated successfully, but these errors were encountered: