Rally-CI is single daemon which listens gerrit events, run tests and
publish results.
It sounds much like zuul but it is not zuul. The primary goal of rally-ci
is simpleness. It does not any git merges, it have not any complex
pipeline logic. Just test every single CR and put +1 or -1.
First of all Rally-CI is simple way to get up and running Third Party CI.
To configure CI you don't need to mess with puppet, jenkins, gearman etc.
Just one single yaml file with some inline bash.
Here is full configuration example with one job "dsvm-rally-block-migrate"
[0]
This job runs two VMs, deploys multinode devstack, and start rally scenario
"boot-and-live-migrate". It will put +1 only if VM actually migrates from
one
compute to another.
Here is current config of Mirantis Rally CI [1], and realtime status [2]
This project was started six month ago as little script, but it still
growing [3]
I believe this project can help people to catch more problems on early
stage.
Also it may be interesting for people who want to practice with asyncio.
Little tutorial "How to run third party CI on a single node" [4]
Change request in openstack-infra/project-config [5]
[0]
https://github.com/redixin/rci-config/blob/master/sample-multinode-dsvm.yaml
[1] https://github.com/redixin/rci-config/blob/master/config.yaml
[2] http://185.8.56.87/
[3] https://blueprints.launchpad.net/rally-ci
[4] https://github.com/redixin/rally-ci/
[5] https://review.openstack.org/#/c/185365/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
