[Vm-dev] appveyor queue is too long

Eliot Miranda eliot.miranda at gmail.com
Thu Jan 3 18:30:30 UTC 2019



> On Jan 2, 2019, at 8:13 AM, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
> 
> Reminder: we also have [skip travis] and [skip appveyor] when we only change platforms specific files, or build instructions.

IMO this info should be in CONTRIBUTING.md alongside the description of [skip ci].  I never knew about this.  I never knew about [skip ci].  Don’t assume users are familiar with script intervals, or github fundamentals, or whatever other mechanism implements the [skip *] facility.  Best to document it in the right place.

Also CONTRIBUTING.md should start with a table of contents.  It is nearly tl;dr

> 
>> Le mer. 2 janv. 2019 à 16:15, Fabio Niephaus <lists at fniephaus.com> a écrit :
>>  
>> 
>> 
>>> On Wed, 2 Jan 2019 at 3:46 pm, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> wrote:
>>>  
>>> Or maybe we don't interrupt jobs that already started?
>> 
>> I think you are right. If that's not the case, we should fix it. Also, we should use [ci skip] more often (but carefully of course).
>> 
>>> 
>>> 
>>>> Le mer. 2 janv. 2019 à 15:44, Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com> a écrit :
>>>> Hi all,
>>>> didn't we configure appveyor to cancel the builds when a newer commit is performed in the same branch/PR?
>>>> 
>>>> Currently, job queue is too deep (and slow)
>>>> https://ci.appveyor.com/project/OpenSmalltalk/vm/history
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20190103/dab0eab6/attachment.html>


More information about the Vm-dev mailing list