Since code check part is available now, could I and Duo prepare to setup
Jenkins CI job firstly?
At fist, start to do the PR check stage according to the workflow option
chosen, then go to the build stage in the next couple of days.
We could optimize all the stages step by step once we start working
on it :
)
He should talk about how this would be implemented.
In the past, we talk about trying to keep as much of the test support
files out of the nuttx/ and apps/ repositories as possible. I would
prefer that we try to keep those repositories as clean as possible
with little or not testing files.
We talking about a third testing/ repository that would be an
environment for testing. In that repository, you could support the
nuttx/ and apps/ directories as submodules and have an environment
that could support unlimited testing without contaminating the nuttx/
and apps/ end-user directories.
Can we please consider this? Let's not put any Jenkins CI in those
end-user directories.
DavidS also suggested moving some of the common tools, such as nxstyle,
out of nuttx/tools to testing/tools. The coding standard check is not
specific to the nuttx/ repository.
Greg
