Submitted by kohsuke on Wed, 2014-12-17 16:15
A lot of us has grown fond of our loyal butler Mr.Jenkins over time, which was created by Frontside and chosen as a result of a logo contest. In the true open-source style, the logo has since evolved into many different derivative works, such as a plugin, a 3D model, and a bobble head.
Our friends at CloudBees are running a #BreakingBuilds social media contest through Jan 5th to have some fun with Mr.Jenkins.
Jenkins User Conference in Bay Area is this Thursday, and one of the new things this year is the mobile app.
There's an Android version as well as an iPhone version. I've installed it locally, and it's very handy for checking the agenda, get more info about speakers and sponsors.
This is a guest post by Craig Rodrigues
The FreeBSD project produces a modern operating system derived from BSD Unix.
In the past 6 months, we have set up Jenkins at http://jenkins.freebsd.org/, to continuously build FreeBSD as developers add new code to the project. This has helped us identify and fix build breaks very quickly.
We have gone even farther by integrating Jenkins, Kyua,
Kyua is a testing framework for infrastructure software.
Bhyve is the native hypervisor that comes with FreeBSD (similar to KVM on Linux).
We use the Build Flow plugin in this example Build flow to do the following:
- Build the FreeBSD kernel and userland on amd64 whenever someone checks in new code to http://svn.freebsd.org
- Create a bootable FreeBSD disk image with makefs
- Boot the image under bhyve
Another day, another SSL vulnerability! Google has announced a vulnerability in SSL v3, and if you are using the "Winstone" servlet container built into Jenkins, and if you are using the HTTPS connector with the --httpsPort option (it is off by default), then you are vulnerable to this problem.
I've just issued a security advisory on this. If you haven't already subscribed to the Jenkins security advisory mailing list, this is a great opportunity to do so.
The advisory includes the target delivery vehicles for the fix and how you can address the problem in the mean time. Inside corporate intranet, where Jenkins is typically used, I suppose there's a degree of trust among participants to make this less of a problem.