liuguo09 commented on issue #2: Multibranch pipeline job example URL: https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-582500074 > I pushed for this a couple times but it seemed full steam ahead for Jenkins. My plan was to wait for some of the ci scripts to stabilize and make my case again. Especially with the free access to windows and osx builds. > > These days of modern CI, I don't know very many other OSS projects that are moving onto Jenkins. Most are there because they have it already and it works. A lot have moved to gitlab, circleci, travis, etc... > > This all said I don't have the time to do the work right now so I should really just stay out of it if others want to. I have just simply tested github action in my fork with https://github.com/liuguo09/incubator-nuttx-testing/blob/github-action-test-1/.github/workflows/ci.yml. And the result in https://github.com/liuguo09/incubator-nuttx-testing/runs/427035372?check_suite_focus=true. It really do a good job. I think it doesn't matter much whether use Apache jenkins or Github actions to do CI. The most important thing would be how to define PR check build, to choose some typical configs build or full build. If check build should behave like full build, then how to reduce the whole build time. In my previous testbuild result with Apache jenkins(apache build server) and Github action(using Github-hosted 2-cores cpu runner), it takes 3~4 hours to finish the whole build process. Use more powerful apache build server or powerful self-hosted github action runner may help. Or make some changes to do out of tree build to speedup parallelize configs build time. Wish more discussion coming : )
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
