How to introduce continuous integration

Goal

Let's understand (1) git, (2) github, (3) packaging, and (4) CI to improve colloboration and productivity among the developers while developing embedded software.

"Review less, merge faster"

1. Fork a github repository
2. How to submit pull request (PR)
3. How to do Tizen packaging (e.g., VD/DTV, DA/FamilyHUB, and MD/Watch)
4. How to Review less, merge faster (TAOS-CI)
5. Practice (e.g., https://github.com/nnsuite/nnstreamer)

Practice Stuff

• Case study

  • https://github.com/nnsuite/TAOS-CI
  • Create your own github repository

• Online manual

  • git - https://backlog.com/git-tutorial/kr/
  • github - https://guides.github.com/
  • Tizen/gbs
    • https://source.tizen.org/documentation/developer-guide/getting-started-guide
    • https://github.com/nnsuite/TAOS-CI/blob/master/packaging/howto-build-package-with-gbs.md
  • Packaging
    • RPM packaging - http://ftp.rpm.org/max-rpm/index.html
    • Ubuntu/debuild - https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#copyright

Action items (Step-by-step prioritization)

1. Use Pull Request (PR, do not use direct merging.!!!)
2. Enable CI System for Review less, merge faster
3. Tizen packaging (optional: + debian packaging)
4. Code refactoring
   • Do not clone sub-folder for another profile/target
   • If need to clone a sub-folder, utlize "git submodule ..." command.
5. Migrate a reository to STAR organization

5 intangible benefits of code reviews

1. Code reviews promote openness
2. Code reviews raise team standards
3. Code reviews propel teamwork
4. Code reviews keep security top-of-mind
5. Code reviews frame social recognition