Upstream持续集成最佳实践概述

1、Continuous Integration (CI) Practices on Zephyr UpstreamUpstream持续集成最佳实践概述AbstractAbstractWe will present a CI system based on several popular open source projectsZephyr(TM) Docker fileJenkins cloudy services DockerTask scheduler system for multi-board testingVirtualization validation systemWith thi

2、s system setting, we build up a CI system with minimum supporting resources and high reliable quality tracking and validation for upstream patches in ZephyrTM BSP support.Continues integration test in ZephyrZephyr project uses ShippableTM as CI framework. LinkIt is not public available, thus customi

3、zation for general users are not possible.e.g. hard to dynamically change the test sets, test stuff is mixed in the same git repo. Connection with other devops system is difficult.No peripheral testing conducted on real board. This problem has deep impacts on real applications quality lifecycle.User

4、 cases for upstreamZephyr repoFunction testContinues Integration TestUpstream tasksZephyr CommunityRequirements on a CI system for upstreamTest on requestCommon & user friendly Stateless processReliable flash mechanismResult processResult storageConfigurable testing scope for boards. Open Source fra

5、meworkTask scheduler Board client which can accept test image and download to boardConsole logger and judging scriptsDocker ftp image for storage logsCI system for upstreamDockers that are used/r/jenkinsci/blueocean/r/stilliard/pure-ftpd/zephyrproject-rtos/ci-dockerfiles.git /_/celeryCI system with

6、databaselog / binary storageZephyr build dockerTask queueDeploymentCloudy ECSAll Dockers deployed heregithub/ bitbucketSCM systemFlash machineTarget boardEthernet PYOCD UART Connect dockersDocker shared volumes /storage/volumes/ Intra docker call docker exec mount /var/run/docker.sock for each docke

7、r containerNote: use docker exec is more preferable if your dockers are running in one server.Glue scripts/hakehuang/zephyr_app_scmJenkins blue ocean configured by pipe line. https:/jenkins.io/doc/book/pipeline/jenkinsfile/We using a glue script to create dynamic pipeline filesPipe file is checked i

8、n each time in a integration test git repoFlash systemA board program scripts are thus designed to support reliable board download/Hoohaha/pymcutkLatest and compromised board program method supportingWorking processOriginal developing branchAdd pipe line fileintegration PRSCM Jenkins triggerBlue Oce

9、anTM call Docker call in zephyr Task queueImage in FTP dockerRun casesresult in FTP dockerJenkins databaseBlue OceanTM UIManual effortsAutomaticExamples- configureExamples- Pipeline viewExamples- logsBenefitsSupport PR integration/regression testing on real board by requestTest scope is customized b

10、y original developerStateless process to developer, async-process. All tasks are automatically queued on one commandLimit extra knowledge sets required, more focus on project itself.Docker usageGitsimple Yaml schematicAlmost zero maintenance resources requiredEasy to port / expand setting can be done in 5 minutesWork SmarterFuture workZephyr project already support gcov data output to console. We can add this feature to testing log parser, and then we can get real coverage data based on def