Java PaaS OpenShift Gets Hudson/Jenkins Environments
The Cloud Zone is brought to you in partnership with Iron.io. Discover how Microservices have transformed the way developers are building and deploying applications in the era of modern cloud infrastructure.
A new release of RedHat's Java PaaS, OpenShift, just became available this week with a bunch of worthwhile new features. The most prominent new feature is built-in workflow support for Hudson or Jenkins. This will give cloud-based developers access to a fully functional Jenkins environment and it's vast ecosystem of plugins.
Big News Update: Jenkins 1.438 can now install Ruby plugins from the update center!
A tutorial by Mike McGrath shows you how to update your RedHat cloud tools and add logic so that after commits are pushed to the JBoss 7.0 "myapp" repo, they will automatically build in Jenkins. In OpenShift, if the Jenkins tests and builds are successful, the new code will be deployed. If it fails, the old code will keep running with no downtime caused by the push.
Other new features include:
- New cartridge (pluggable component) type "raw" - used for raw computing power with no web interface. Can be used as a builder for Jenkins or for process jobs.
- Custom domain support. Command for new domain: $ rhc-ctl-app -a myapp -c add-alias --alias newdomain.example.com
- Local mirrors added for jbossas-7.0, wsgi-3.2 (python), and perl-5.10.
OpenShift competitor, CloudBees, had Jenkins cloud instances when the company first began. It's because CloudBees was initally somewhat focused around being a Hudson/Jenkins in the cloud PaaS offering. However, OpenShift is well placed to benefit from JBoss' huge array of developer tools that it has nurtured and experimented with over many years. Their support of Java EE is also outstanding in many of their technologies.
If you're an Eclipse user who is looking to give OpenShift a whirl, I recoomend reading this tutorial on the Eclipse OpenShift plugin.