Hi
Share the full picture with all of you about Apache CarbonData CI.
--------------------------------------
1.CI Environment
For supporting more complex CI test(like cluster), we built the Apache CarbonData Jenkins CI which is running in cloud machine machine with IP
http://136.243.101.176:8080/ . Anybody can access this machine and check the build status and result.
New github user CarbonDataQA is created for CI activities and status updation of PR builds are done by this user.
2.Pull Request Builder
This is a job in Jenkins CI with name ApacheCarbonPRBuilder. This job is triggered for every PR update/create.
All are committers are Admins for this plugin.
When a new pull request is opened in the project and the author of the pull request isn't white-listed, CarbonDataQA will ask "Can one of the admins verify this patch?".
● "ok to test" to accept this pull request for building in CI, so any updates in this PR will trigger build automatically.
● "add to whitelist" to add the author to the whitelist, all future PRs from this user can be built automatically.
● "test this please" for a one-time build
● "retest this please" to rebuild If the previous build fails for other various reasons.
Once the build is finished, the status of the build is commented on the same pull request as follows
● Build Success
Build Success, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/33/● Build Fail
Build Failed, Please check CI
http://136.243.101.176:8080/job/ApacheCarbonPRBuilder/33/Regards
Liang
Locked
