[Plone-testing-team] p.a.dexterity job on jenkins.plone.org

David Glick dglick at gmail.com
Fri Apr 19 16:17:16 UTC 2013

On 4/19/13 1:33 AM, Timo Stollenwerk wrote:
> Hi David,
> I just created a new Jenkins job for p.a.dexterity:
> http://jenkins.plone.org/view/Packages/job/plone-app-dexterity/
> My idea is to create Jenkins jobs for each coredev package, to be able
> to give developers a faster response to their commits, since the coredev
> jobs run over an hour. In addition, these jobs provide information about
> the changes (that might have caused a test failure):
> http://jenkins.plone.org/view/Packages/job/plone-app-contenttypes/changes
> These single package jobs also run code analysis and code coverage. So
> far I set this up for a couple of selected packages, to see how this
> could work:
> http://jenkins.plone.org/view/Packages/
> These jobs are marked "unstable" (yellow) when there is a single PEP8
> violation and if code coverage is below 90%. With this in place we could
> define certain standards (minimum code coverage, number of "allowed"
> pep8, jslint, csslint violations, etc.) for core packages that Jenkins
> tests.
> Since this is a way to ambitious goal to achieve for all coredev
> packages, we can define different quality standards for the packages if
> we want (or use Jenkins to mark those packages differently).

Sounds ambitious indeed, but a worthy direction to be heading.

> My idea would be to fist define a certain quality standard and make this
> a requirement for new packages (and for PLIPs as well). At the same time
> we could try to leverage existing packages to the new standards one by one.

The framework team recently adopted the style guide from plone.api as 
the official one for new Plone code.

> I would like to hear your thoughts on that and if you think this could
> be useful for you and for the fwt.
> Cheers,
> Timo
> ps: it would be awesome if you could have a look at the dexterity test
> failures on the Plone 4.2 job:
> http://jenkins.plone.org/job/plone-4.2-python-2.7/
I'll take a look.

More information about the Plone-testing-team mailing list