On Tue, 7 Mar 2017, Dan Watkins wrote: > Hi Josh, > > On 07/03/17 12:21, Joshua Powers wrote: > > Yesterday I enabled automated CI reviews of cloud-init merge requests. > > These reviews will run the included tox-based tests across all supported > > architectures and validate that a description or commit message is set in > > each new merge request. > > This is excellent news! \o/ \o/ \o/ > > > The tests are run on the Ubuntu Server Team Jenkins where the results are > > available for view under the cloud-init-ci job [1]. For those new to > > submitting merge requests the process is documented under the cloud-init > > hacking page [2]. > > Will the CI job comment on/review merge proposals, or do reviewers need > to manually examine the output in Jenkins?
Not sure what you mean. See https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/318800 There the bot comments like https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/318800/comments/833629 You do have to click through to see test output though. I think that is what you were asking. You do have to look at the console run. I don't really think posting all of the output even of the failed run[s] would make anything more clear. Scott -- Mailing list: https://launchpad.net/~cloud-init Post to : [email protected] Unsubscribe : https://launchpad.net/~cloud-init More help : https://help.launchpad.net/ListHelp

