Home

Welcome to the TAOS-CI wiki!

The picture above shows how the continous integration and deployment are related to each inspection process before merging the pull request into a mainline branch (e.g., Master) finally.

• Red rectangle: It means that the inspection process has to go back to a start point.
• Green rectangle: It means that the inspeciton process can to go to next setp without a return process.

Release Plan

• https://github.com/nnsuite/TAOS-CI/wiki/Release-Plan

CI Server

• CI Bot ID for webhook API
  • nnstreamer repository: https://github.com/nnsuite-ci (by Sewon Oh)
  • TAOS-CI repostiroy: https://github.com/taos-ci (email: [email protected])
• CI Web Server: (Sewon Oh has issued the below hostnames at http://freedns.afraid.org)
  • http://nnsuite.mooo.com
  • http://taos-ci.mooo.com
• A tool to import a github issue and pull request from github enterprise to github.com:
  • https://github.com/leemgs/github-issues-import-ng

Demo (Youtube): Case study

• How to install TAOS-CI on Ubuntu PC - W.I.P (3~4 minutes)
• How to write new plugin module - https://youtu.be/_FvMmvJSBq4 (3 minutes)
• How to submit a pull request on TAOS-CI - https://youtu.be/2L2Hiy1qIdA (4 minutes)

How to re-trigger a pull request

Sometimes, contributors meet unexpected CI failure even though they submit correct PRs. In this case, please re-trigger CI checker by appending @open sesame mm/dd hh:mm of your PR title.

• Example: [segmentation] update model & change IPC - @open sesame 08/15 18:27

Supported plug-in modules

• TAOS-CI Plug-in Modules

Reference

• https://developer.github.com/webhooks/