JEP-200 has been integrated into Jenkins weekly builds
and (if all goes well) will be a part of the next LTS line.
In a nutshell, this change is a security hardening measure
to be less permissive about deserializing Java classes defined in the Java Platform or libraries bundled with Jenkins.
For several years now, Jenkins has specifically blacklisted certain classes and packages according to known or suspected exploits;
There are upcoming changes in Jenkins "core" which may require extra steps
when upgrading Jenkins. If you use configuration management for Jenkins
agents, please read this announcement carefully.
If you have ever seen messages like "Channel is already closed" or "Remote call failed" in your build logs,
you have already met Jenkins Remoting.
Remoting is an agent executable (aka slave.jar) and a library implementing the communication layer between...
In response to the zero-day vulnerability we fixed in November, I wrote the following:
Moving forward, the Jenkins security team is revisiting the design of the Jenkins CLI over the coming weeks to prevent this class of vulnerability in the future.
If you are interested in participating in that discussion, please join in on the jenkinsci-dev@ mailing list.
In early February, several project contributors met after FOSDEM...
Setup and Manage iOS & Android infrastructure for CI with Jenkins
March 2018 Philadelphia JAM
Day of Cloud Native warm-up!