On Fri, Jan 10, 2020 at 2:12 PM Justin Mclean <jus...@classsoftware.com> wrote:
> Hi, > > > 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 > > I can add people to that as needed. I created jobs and given access o > people in the past. > Ok, I would like to be added in order to collaborate, if other people involved agree. Not urgent by now. > Could it be possible to make the configuration read-only, even without > > account or with a restricted one? > > I'm not 100% sure that can be done, but you have a history of changes in > Jenkins so it’s not hard to manage. > Ok, if not possible, I guess is ok to give a normal account, and just rely on accountability of changes. Another request: is there any document describing the things we are expecting to check in the CI for each commit/PR and for each release? I guess that at the very least we want to test the tests in https://github.com/apache/incubator-nuttx-apps/tree/master/testing and in the examples, for the most important architectures. Thanks, Miguel
