liuguo09 commented on issue #2: Multibranch pipeline job example URL: https://github.com/apache/incubator-nuttx-testing/pull/2#issuecomment-581977370 > @davids5 @patacongo @jerpelea > > Totally agree, and that was and is the original intention. This is just a skeleton to build upon: I think we should merge this pull request, and then, once it is being triggered correctly by pull request according to the agreed workflow, we could improve it by changing this groovy shared library (we won't need to ever (or seldom) change the `tools/Jenkinsfile` in core OS repo `apache/incubator-nuttx` needed to trigger the multibranch pipeline). > > For example, I just used the `cibuild.sh -b full` as in the nightly, but in fact should be using the short list: `cibuild.sh -b check`. > > We can iterate this aside of the core OS repo. For example, it could be easy to modify the groovy script to make it look like the parallelized pipeline @davids5 have shown. > > To do that, another Jenkinsfile will be added to testing repo itself, and another multibranch pipeline should be created, so that the pipeline itself can be tested (from pull request branches to `apache/incubator-nuttx-testing`) independently from the core OS stable pipeline (the defined in `master` branch of `apache/incubator-nuttx-testing`). (By the way, I need to add the "meta" pipeline testing job as well, when I have time). > > But not having still these jobs defined already in builds.apache.org makes it difficult to test/iterate by now. > > Hope that this clarify my proposal. That's right. As @maht said, cibuild.sh and testlist files are designed in mind to support both nightly build and check build with `cibuild.sh -b full` and `cibuild.sh -b check`. Start simple, one freestyle NuttX Nightly Build job has been setup in builds.apache.org to verify nightly build firstly. Then check build which hook with incoming PR should be available later. As for build time, with ccache enabled and powerful build machines(for example, donate powerful machine), I think it could be reduced more. I also agree that it would be better to use jenkins pipeline way for more advantages as @maht and @davids5 mentioned.
---------------------------------------------------------------- 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
