Iori stands for successfull builds.
Kyo stands for other build states, such as
Every action in the fight is determined by 5 finished jobs in Travis CI:
passed: total success, Iori gives a super special move.
passed: big success, Iori gives a heavy punch
passed: small success, Iori gives a light punch
passed: small failure, Kyo gives a light punch
passed: big failure, Kyo gives a heavy punch
passed: total failure, Kyo gives a super special move.
A short video to show such an interesting fight:
The script is written in Python2. Thanks to the nice Travis builds websocket provided by Thomas Durieux, all Travis build events are fetched regularly. Then all
job_finished events are added into a queue. Another subthread picks 5 builds from the queue every time, then calculates fighters’ action based on the rules above. These actions are sent to the game emulator by another subthread. During my testing, KOF-97 is running in a Wine environment.
pip install websocket_client
sudo apt-get install xdotool
This is just a visualization idea about Travis CI data. No matter a job is
passed or not, it helps developers to test their project. So don’t take the fighting result seriously, just enjoy a KOF-97 fight controlled by CI data :)