[Plone-testing-team] meeting notes during bicycle sprint

Gil Forcada gil.forcada at freitag.de
Mon Mar 23 22:10:13 UTC 2015


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

during the bicycle sprint[1] Timo and me sat down to discuss the
foreseeable future of CI (focused only in Jenkins actually).

Here are some notes that I took during that meeting:

- - workflow job[2]: we still need to wait for xvfb to be able to run
everything from a single job, right now the testing job[3] runs core
and at tests[4]

The pipeline that we envision would be:
- - (sequential) checkout -> bootstrap -> single package test
- - (in parallel) core tests, AT tests, robot tests

Reporting will be at any time during the sequential phase and at the
end of all parallel jobs.

The important thing here is that the sequential part should run in
less than 10 minutes, which most probably will catch 80% of the
regressions (regressions on the package itself), the parallel part
takes (right now) around 30 minutes.

So the whole pipeline should be finished by 40 minutes at maximum.


We also discussed a pipeline for single packages, not for testing but
for all other sorts of CI/QA stuff. The pipeline envisioned here would b
e:
- - code analysis -> internal release -> docs -> coverage

So basically do code analysis of the package, check that doing a fake
release works (broken releases due to MANIFEST.in not set it properly,
missing files, etc) building the docs and checking for errors and
finally to get test coverage so we know how good/bad the testing
coverage is.



We would also use this single package jobs for playing with the github
API so in the future, once is stable and working properly we can get
reports travis-like directly on github. Which is mostly what everyone
wants.

Once that stable enough we could add that to the pull-request job,
which would it be great to have :)


Further down the road we need to discuss with Sven and Steve about how
to integrate automatically building docs.plone.org on a green build
(so we could fix documentation issues live from a git commit) and how
to build testing/trial images (docker, what not) out of any green
build also, so that we allow non-coders to see the current status of
plone. That would be great for designers working on theming, etc etc


Lastly, it was a pleasure, as always to meet and discuss with Timo,
which by the way, please add anything that I forgot :)


Happy testing,
Gil

[1] http://www.coactivate.org/projects/bicycle-sprint/project-home
[2] https://wiki.jenkins-ci.org/display/JENKINS/Workflow+Plugin
[3] http://jenkins.plone.org/job/workflow
[4] https://github.com/plone/jenkins.plone.org/blob/master/flow.groovy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJVEI9FAAoJEM2P68YKpRQl6t8P/j0Iui5hfjF7gmLetdoYP6XH
Yo4R1zHgzQ9IzKXxYYhfk6dGD9HbHsSWp9c0qvWUq/jr6iuK2XTflEAlKyiwTliy
WNl6bbyOl1s8A12sSh1wnWEguk9EDnZHaoTw5MNkox+wwdOK6diK5inaDfC+t+Zs
3kdaW3lzlEMQcxr40cqVj9J/trpO5ysjeqG1Ob7PGXSQsRFc2a0ZXa9SFDlGAVPg
hi8VntUyTgvsGLk6NR5ydlouu8dqi2mOQRIEhrqfuREXpOgtXnCBGS0UqzWQ4QFj
rThm7APOqugaEaov3pG7bYyUaFvr0DIKKO4I8HmwrErWUleZ74mAI38hK+p09his
Llh2ilQpKeNFBK+A6qtnBEoKaIunJqbv1fsbdSCmDz9y8JeCCoPG4IOtnM6OpBM8
JeNPu/iLhO89h/AZt1/+yShVOrIRV5oTgMUiR6hq2Kxmi32Maxg0s9Z06Vqu3Ojb
oHyWngrv3afN/rVpy1rQV+gB0KmzfnJYqPpk/33TZ3RHIXMxmW4dJwXTmuZ3XZ9l
gHoDEqDFAMUIRlDuHYdv5IZxnSNv4BevxdD4gZYrrHTDQHvD/W6Q4OKh0AQ6N5f9
3qhl3K70ZeaTXxehNE7k31I6j3pKfeyMARo2RMJM9gWqyRZ0NBNa0CqRv9D5+1aC
PKHqeKJ2iriA/qFtCk94
=DUY2
-----END PGP SIGNATURE-----


den Freitag gibt es ab sofort auch digital! Jetzt stöbern auf: https://digital.freitag.de


Diese Nachricht (inklusive aller Anhänge) ist vertraulich. Sie darf ausschließlich durch den vorgesehenen Empfänger und Adressaten gelesen, kopiert oder genutzt werden. Sollten Sie diese Nachricht versehentlich erhalten haben, bitten wir, den Absender (durch Antwort-E-Mail) hiervon unverzüglich zu informieren und die Nachricht zu löschen. Jede unerlaubte Nutzung oder Weitergabe des Inhalts dieser Nachricht, sei es vollständig oder teilweise, ist unzulässig.

This message (including any attachments) is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error please contact the sender (by return E-Mail) immediately and delete this message. Any unauthorised use or dissemination of this message in whole or in part is strictly prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-testing-team/attachments/20150323/d6be31e5/attachment.html>


More information about the Plone-testing-team mailing list