Test your add-ons against development versions of Plone

Hi all,

I would like to get some attention from all add-on developers about these new jenkins jobs that I created (for a long version see http://gil.badall.net/2017/04/30/updates-from-the-plone-testing-and-continuous-integration-team/).


If you have ever used the pull request jenkins jobs, is quite the same, but for add-ons.

Tell Jenkins where's your add-on (only git by now) and which branch to use and it will run the tests on it.

Once finished you will get a mail reporting the status of the job.

Please let me know if it works for you as well, what are the problems, what could be improved, etc etc

Happy hacking!


And a comment is added to the latest commit with the result:

we have being doing this with Travis CI for many years; can you explain why should we use this new approach instead of the current one?

You are testing against the next unreleased version of Plone?

What we do here is testing your add-on against the current checkouts of Plone, rather than against the last released version.

All the discussion about the -pending releases KGS are moot, more or less, with this new Jenkins jobs.

If you have your own way and it works for you, please keep it, you are not forced to use them if you don't want to.

no, and I don't want to do that, but probably there may be others that want it (CC @idgserpro).

the pending stuff is neither a problem for me: typically minor Plone releases are bug fixes that should not break anything; that's why we can test on the last stage only.

major release are already covered in our schema: we already test against Plone 5.1 for instance.

This jobs are not actually meant to replace your CI, you don't want to block a pull request because it does not work on an unreleased version of Plone, but the use case, for me at least, would be to use it to check if some new features that got added into Plone recently break your add-on, so you have a heads-up before the final release.

1 Like

It would be nice to have this information at docs.plone.org, just don't know which section would be the best place.