Hey, * Bruno Oliveira <[email protected]> [2016-01-15 00:15:39 +0000]: > I created a small repository[1] which only contains appveyor and travis > scripts which simply use "devpi test" to test and publish results for the > pytest 2.8.5 release[2] in Travis and AppVeyor.
Thanks! This is about what I imagined when talking about it in the Hangout. I wanted to write a more detailed proposal to the ML but never got to it ;) As I said there, the devpi part was the most painful point of doing the release for me (not because of devpi directly, I think). I had to set it up on multiple machines, and had various trouble ([1]) which nobody else seems to be having, which why I'd like a reproducible environment. [1] https://github.com/pytest-dev/pytest/issues/1114 https://github.com/pytest-dev/pytest/issues/1115 https://github.com/pytest-dev/pytest/issues/1116 Florian -- http://www.the-compiler.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
signature.asc
Description: Digital signature
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
