How about just keep two separate git repositories (apps and nuttx projects) instead of add a parent knot repo with apps and nuttx as sub-modules? As to jenkins CI, I haven’t found proper github plugin to get PRs from multiple repos(especially PRs dependency in apps & nuttx ) in one Jenkins job. Before that, I wonder whether we could keep it simple and directly, create one jenkins job for apps and another jenkins job for nuttx to process PR trigger accordingly. Just make sure the jenkins pipeline or build script to sync both apps and nuttx repos, then pick the apps or nuttx PR to do full build.
Since nuttx and apps projects keeps same as before, developers adapt to github workflow as usual: 1 fork the official apache nuttx & apps projects in github 2 git clone your fork projects locally 3 edit locally and then git commit to local branch 4 git push to your github fork nuttx/apps branch 5 issue one pull request from your fork nuttx/apps to apache nuttx/apps master branch 6 jenkins CI auto-trigger: style check, build or test, if failed, go to step 3, continue 3 ~ 7 7 PMC start to review PR, review ok, merge to master; or review failed, go to step 3, continue 3~7 Detailed info about GitHub workflow: https://help.github.com/en/github/collaborating-with-issues-and-pull-requests <david.sidr...@gmail.com> 于2019年12月17日周二 下午5:36写道： > [DISCUSS - NuttX Workflow] > > I am creating this thread to discuss what we as a community would like to > have as NuttX Workflow. I have also created [REQUIREMENTS- NuttX Workflow] > I am asking us to not add discussion to [REQUIREMENTS- NuttX Workflow]. > Please do that here. > > As this discussion evolves we shall create requirements and add them > to the [REQUIREMENTS- > NuttX Workflow] thread. > > Please use [DISCUSS - NuttX Workflow] to propose and discuss the ideas > and experiences > you have to offer. > > Be detailed; give examples, list pros and cons, why you like it and why you > don't. > > Then after the requirements are gathered in one place and discussed here > then can vote on them. > > Thank you. > > David >
