Hi all,
looking at jenkinsci account on the github i've got an idea to create
pytest 'company' github
account and ask plugin developer to move plugins under that account
This could help to `protect` the plugin development somehow, also will help
a lot in terms of the
support, as `board` members
On Fri, Jul 25, 2014 at 21:27 +0200, Anatoly Bubenkov wrote:
Hi all,
looking at jenkinsci account on the github i've got an idea to create
pytest 'company' github
account and ask plugin developer to move plugins under that account
This could help to `protect` the plugin development somehow,
+1
I think having one place for the plugins is good. If you when need to
change something in py.test you can do a quick search through the plugins
and see if they will be affected.
It will also allow for more collaboration between plugin developers.
Harro
On 26 July 2014 12:41, holger krekel
challenge accepted :)
On 26 July 2014 12:41, holger krekel hol...@merlinux.eu wrote:
On Fri, Jul 25, 2014 at 21:27 +0200, Anatoly Bubenkov wrote:
Hi all,
looking at jenkinsci account on the github i've got an idea to create
pytest 'company' github
account and ask plugin developer to
Hi all,
I managed to get it to work by explicitly importing pytest and py modules
explicitly. The version that worked for me is in the same gist link I sent
earlier (https://gist.github.com/nicoddemus/5458ca3fc5241cedaff3), which I
made public so others that run into the same problem can find it.