On Fri, Jan 10, 2020 at 4:24 AM Haitao Liu <liugu...@gmail.com> wrote:
> Thanks Miguel share your approach. We'll look into it, the aim for NuttX > is keep nuttx/ and apps/ user-end projects > clean and do not mess up with CI stuffs. Thanks for the feedback. And yes, separate repo for CI stuff is a reasonable approach. And now prepare to use Apache > Infra Jenkins CI firstly. > Yes, probably the best approach is to prepare CI jobs in a traditional way, and once it is almost stable and you and people involved have less work with it start to translating it to something versionable as the Jenkins Job Builder definitions. This way the transition curve is easier and avoid interfering with the priority goal of having a working CI. One request: I checked the Jenkins and it seems that the job configuration is not accessible without having an account, and you have to be a committer and must be a member of the hudson-jobadmin group (according to https://cwiki.apache.org/confluence/display/INFRA/Jenkins#Jenkins-HowdoIgetanaccount?). Could it be possible to make the configuration read-only, even without account or with a restricted one? This way it would be easier for me and other people to help and review job definitions and I could help to create job builder definition templates in the meanwhile, based on the jobs the committer is creating manually with the UI.
