[Vm-dev] why are the builds cancelled
Alistair Grant
akgrant0710 at gmail.com
Mon Mar 19 08:41:50 UTC 2018
Hi Tobias,
On 19 March 2018 at 09:38, Tobias Pape <Das.Linux at gmx.de> wrote:
>
> Hi,
>
>> On 19.03.2018, at 01:56, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>>
>> Hi,
>>
>> Travis isn't building new commits and I don't know why. Can someone update the README.md for opensmalltalk/vm with a pointer to an overview of the Travis CI infrastructure so that someone could work out why things aren't working?
>
>
> Things are working ;)
> What happens is: we're using build stages to minimize load on travis and to get faster feedback.
>
> Let's take this as an example:
> https://travis-ci.org/OpenSmalltalk/opensmalltalk-vm/builds/354870586
>
> We currently have four stages:
> - Linux builds
> - Mac builds
> - Stack builds
> - Linux32armv6 builds
>
> Each stage will only start iff the previous stage completed successfully, essentially saying "if those builds did not run, don't even bother looking at me"
>
> So, since the Linux builds did not complete all (in fact, only one did), all subsequent stages are ignored.
>
> This actually ensures that we get swifter response, as later builds are more likely to run.
>
> Does that help?
While we're on this topic, would you mind explaining the logic for
transferring builds to bintray?
There hasn't been an update to
https://bintray.com/opensmalltalk/vm/cog/ since March 8th, and I'm
fairly sure there have been successful builds on travis.
Thanks,
Alistair
More information about the Vm-dev
mailing list