cloudsidedev / cloudsidedev/appside
CI
- Dominant language
- Python
- Stars
- 38
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
We want to be able to test latest AppFlow code based on [Continuous Integration](https://en.wikipedia.org/wiki/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`](https://github.com/ttssdev/appflow/blob/master/build/Jenkinsfile).
The stages of the pipeline process (thanks to @sneaker for suggestions on this), should run in parallel and perform this specific tasks:
- create test [LXC containers on Proxmox](https://pve.proxmox.com/wiki/Proxmox_VE_API#Step_by_step_example_of_LXC_creation_using_the_API) or new test [VMs on FreeNAS Corral via bhyve](https://github.com/freenas/cli/blob/master/README.rst#vms).
- provision those "nodes" with AppFlow, via `ssh`, against the latest `mrrobot` example configs.
- report build success/failures on slack.
We should trigger the LXC/VM creation via API, like `pvesh` on Proxmox and `vm` on FreeNAS Corral, we also could use `curl` REST API calls.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.