[core-workflow] Status update for Kallithea based workflow PEPs
Nick Coghlan
ncoghlan at gmail.com
Mon Feb 9 22:02:38 CET 2015
On 10 Feb 2015 06:39, "Brett Cannon" <bcannon at gmail.com> wrote:
>
>
>
> On Mon Feb 09 2015 at 3:30:32 PM Antoine Pitrou <solipsis at pitrou.net>
wrote:
>>
>> On Mon, 09 Feb 2015 15:34:02 +0000
>> Brett Cannon <bcannon at gmail.com> wrote:
>> > If you're taking ideas then I vote for stuff like
>> > getting Buildbots up using containers so that we can download the same
>> > containers as developers and run them under, e.g. Valgrant to do local
>> > testing on the OS the container is targeting?
>>
>> As long as the tested platform can run in a container... (or perhaps
>> you meant a VM?).
>
>
> I did mean container but VMs also work. I realize this won't work for all
OSs, but it does work for enough to warrant looking into since containers
have better workflows for local testing when something does fail.
The main overhead is actually maintaining your stable of base images, and
the infrastructure for doing that with containers independently of
DockerHub is currently still fairly immature.
At this point in history, we'd probably be better off hooking up the
BuildBot master's VM worker support up to the PSF's Rackspace account - our
throughput is low enough that the VM vs container overhead shouldn't matter.
There may still be value in enabling local container based testing for
CPython itself, though. At the very least, between Vagrant and Docker we
should be able to automate *local* testing across various POSIX systems
without affecting the host system (beyond installing Vagrant and
potentially VirtualBox), and Windows folks may even be able to figure out
how to automate that side of things as well (at least with an active MSDN
subscription).
Cheers,
Nick.
>
> -Brett
>
>>
>>
>> Regards
>>
>> Antoine.
>>
>>
>> _______________________________________________
>> core-workflow mailing list
>> core-workflow at python.org
>> https://mail.python.org/mailman/listinfo/core-workflow
>> This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct
>
>
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20150210/0f04bfc8/attachment.html>
More information about the core-workflow
mailing list