Open Stack

On 11/08/14 13:20, Andreas Jaeger wrote:
> On 08/11/2014 05:26 AM, Tom Fifield wrote:
>> On 10/08/14 22:21, Andreas Jaeger wrote:
>>> With the addition of a non-voting check for linked URLs, we need to
>>> touch Jenkins jobs and our tox.ini everywhere. I suggest to do this
>>> differently: Combine the tiny voting jobs in one job and do the same for
>>> non-voting jobs.
>>>
>>> So, instead of:
>>> * check-syntax
>>> * check-niceness
>>> * check-deletions
>>> * check-links
>>>
>>> we would have:
>>> * check-voting
>>> * check-non-voting
>>
>> May I ask what would be posted on the review comment? Would we still
>> have a posting of all of the various job results {syntax, niceness,
>> deletions, links} and FAIL/PASS next to them? Or would it be just
>> {voting, non-voting} PASS/FAIL.
>
> It would be
> voting: PASS
> non-voting: PASS
> check-build: PASS
> check-lang: PASS
>
> And then you need to click on the link for details - like you do today -
> but also to read out which check failed,

Ok, if that's the case, my preference would be to leave it as it is - 
with each check giving its own explicit pass/fail.

Aside from my personal preference, I believe explicitly separating the 
tests is more friendly for new users.


Regards,


Tom