Neyts Zupan (@zupo.bsky.social)

In 2012 I gave a talk on using Travis CI for @plone.org add-ons. Just drop in a config file, hook it up to GitHub, and you’re set. For small open-source projects, it made continuous integration much simpler. www.youtube.com/watch #CI #OpenSource #TBT #Plone

loading . . .

Nejc Zupan: Travis: CI: easy and fun CI for your Plone packages Disclaimer before I start: I've been using Jenkins for about two years now. Huge builds, such as those found on jenkins.plone.org, are not the target use-case for Travis. Neither are private builds, where all code needs to be kept in-house. That being said, there is a gazillion of simple Plone add-ons that only add a few content types and some views. These could benefit greatly by using Travis CI. Travis CI is a Continuous Integration service for the Open Source Community. As of this writing, Travis CI has run +750k tests for +10k open-source projects. For any open source Plone add-on hosted on GitHub, you can get Travis CI for free. You don't need to worry about running a separate server for your CI needs, just go to your GitHub repository, add a short .travis.yml config file and enable Travis CI service hook. It really is this simple. In the talk I'll show you how to use Travis CI for Plone packages with ease, provide pointers for what to do if you reach a build timeout and show some packages that are already using Travis CI so you can use them as a point of reference. Then I'll discuss how we (as a community) can use Travis CI for collective.* and possibly plone.* packages, followed by how one can use Travis CI for private repositories on GitHub (this is still in beta, hopefully Travis CI Pro will be out before the conference). https://www.youtube.com/watch?v=HsGLLGeXFOU&t=1878s