One of the first things people do when they start thinking about implementing DevOps best practices is setting up continuous integration and continuous deployment (CI/CD) tooling. So that’s just what we did with the Professor M School. (Not sure what I’m talking about when I say the “Professor M School?” Check out my earlier blog post Introducing Professor M’s School for Gifted Coders.)
We’ve set up CI/CD with not one but two popular tools: Travis CI and Jenkins. As you decide which tool to use, consider the following tradeoffs. Travis CI is hosted online so you don’t have to set it up yourself. Open source projects can leverage Travis CI for free, but closed source projects will have to pay. Jenkins requires you to set up and manage the app yourself but is free for all projects.
Automated build inside of Jenkins
We’ve set up the same basic flow for both CI/CD tools:
- Run the automated tests
- Build the Professor M module loadable packages
In addition, the Travis CI build is configured to post the Professor M module loadable packages to the GitHub releases page whenever a commit is pushed to the master branch.
You can learn more about how we’ve implemented CI/CD in the Professor M School’s Readme:
You can also explore the results of our latest Travis CI builds at https://travis-ci.org/sugarcrm/school/.
We hope you’ll be able to leverage the work we’ve done to setup CI/CD with Travis CI and Jenkins in your own projects!