Merge & Build automation

[ILyoan]

RFC: Merge & Build Automation.

Summary

Introduce a automated build system for continuous integration. There are several well-known build systems such as buildbot, jenkins, hudson, and etc. By using automated build system, we can not only reduce our merge or integration cost but also eliminate human mistakes.

Motive

The process of source integrating is a work of routine. But it requires for people delicate work from start to end to finish without making any mistake. Unfortunately we human being make mistakes even more when the work is a kind of routine. And also it takes a time to be done.
By using automated build system, we are free from such matters. The most of the steps in a process of source integration - except an important step, reviewing - are programmable.

What can be done by automated build system

Automated build system may conduct following routines.

• Daily building and reporting result.
• Daily testing including benchmark and reporting result.
• Build by trigger.
• Test by trigger.

It also can do followings in conjunction with github web hook API.

• If there is a new issue registered, report it.
• If there is a new pull request, report it.
• If there is a reviewed pull request, build it.
  • If the build and test finished successfully, merge it to master.

[seanshpark]

sounds good!

[ILyoan]

In today's discussion, a neat CI tool called Travis was adverted.
Let's reconsider build automation once this project is publicly opened. At this time we don't have enough needs and resources to configure build automation.

[lemmaa]

I agree. I also check the way to use Travis with private GitHub repository.

[ILyoan]

Today we integrated with jenkins run on http://83.69.213.178:8888/job/IoT.js

Triggering build using webhook is not setup right now which can be resolved in more specific issue.

Close this issue as resolved.