Travis failures and other CI solutions
Marius Vollmer
marius.vollmer at redhat.com
Mon Aug 24 08:55:26 UTC 2015
>> This is weird. How do they manage to not fully support inotify? Is it
>> a weird/broken filesystem? Some absurdly low limits somewhere?
>
> NFS.
Oh, I see.
> sudo can run in a container. It's just the Travis containers that don't
> allow this. [...]
Ok, so Semaphore does allow it and we don't need to change the tests?
That is another big pro.
>> And switching to containers in Travis might just make the weird "write
>> error" bug disappear, I guess.
>
> But more importantly the Travis containers have an ancient operating
> system (from 2012) and can't be updated (due to no root access).
Yes, the pros are very strong.
More information about the cockpit-devel
mailing list