Important Version Two Cartidge Information for Jenkins Users
May 20, 2013 | by
If you've been following my posts on the new cartridge format: part 1 and part 2, you know that big changes are afoot. We're working as hard as we can to make the transition as smooth and seamless as possible.
Some users may be required to make changes to their applications and this blog post is aimed at people with Jenkins applications. Jenkins provides continuous integration for those who want to have tighter control over their builds, logging, and better resource handling. If you aren't using Jenkins or have no interest in continuous integration, you can stop reading now. Go read up on Jenkins or give it a try, it's well worth it!
When the version 2 cartridge updates happen the week of June 3, 2013, you'll want to follow these steps to make sure Jenkins continues working for you:
Make note of any custom changes to existing jobs
Rename the job
Remove the jenkins-client from your applications
Re-add the jenkin-client
Everything should work again. Those who have customized their jobs will want to copy any customizations from their original jobs they renamed into the newly created jobs.
As we work our way out of developer preview we try to find ways to make sure changes are consistent and compatible but it's not always possible. Sorry for the inconvenience, if you have any questions or comments reach us at email@example.com
We’re always looking for ways to provide a better user experience. With growing numbers of users across the globe, localization has become increasingly important. In OpenShift 4.7, we’re introducing ...
Today, I am pleased to announce the general availability of Red Hat OpenShift 4.7. Based on Kubernetes 1.20 (and CRI-O 1.20), OpenShift 4.7 has made progress on a few new features and functionality ...
When we graduated OpenShift Virtualization from Tech Preview to a Generally Available feature with OpenShift 4.5, we had a good idea how development teams would use virtual machines in Kubernetes to ...