[ibmz-ci-announce] Improvements to Jenkins+Docker integration

[Lance Albertson]

All,

I wanted to announce that we've deployed a new method for running your CI
jobs on our Jenkins environment. We've installed the Docker Custom Build
Environment [0] plugin and configured our docker nodes to properly use the
plugin. This will allow you as users to deploy any image you would like
without the OSL needing to configure the image on the admin panel. This
also gives you a lot more flexibility in how you can use the system
hopefully. In addition, this should help resolve load balancing issues we
currently have with the current setup.

We've created new documentation [1] describing how to use the plugin and
interact with our system. This document is targeted for our POWER CI
system, however the IBMZ CI system is setup the same. The primary
difference is that you should be using the 's390x' label which will balance
the load between the two s390x nodes we have. We are still maintaining the
same docker images if you'd prefer to use them. If you want to use your own
images, please read the documentation on what changes you need to make to
ensure it works correctly. We will make a new document for s390x soon but I
wanted to get this information out ASAP.

We would like everyone with jobs to migrate to using this plugin ASAP.
After May 17th, we will migrate the remaining jobs over to the new system
and ensure that those jobs are still working. We will be deprecating the
previous docker system by the end of May. I've also updated the example
"test" jobs if you would like to see how they work.

If you have any questions, please let me know!

[0] https://plugins.jenkins.io/docker-custom-build-environment
[1] https://wiki.osuosl.org/powerci/docker.html

-- 
Lance Albertson
Director
Oregon State University | Open Source Lab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/ibmz-ci-announce/attachments/20190503/25307d60/attachment.html>