General

General bucket for non-specific content

Munich Hackathon

It's been a while we had a hackathon in Germany. Let's get together, get some coding done, and get to know fellow Jenkins developers! The date is June 15th Saturday.

TNG Technology Consulting, where Stefan Wolf (dependency graph viewer plugin, etc) works, will be hosting us (thanks!)

We'll try to arrange some themes or agenda, based on who's coming and how many of us will be there. For example,

  • If there are many people who have never done a plugin development, we can do a plugin development tutorial.
  • If we see a concentration of devs in a specific area of Jenkins (say mobile), we can try some focused development in a specific area.
  • If you have things you need from the core to do what you want, this is the chance to get that implemented on the spot!
  • If you want to see a certain development happen in Jenkins but don't know how, please make a pitch to us in the form of presentations (short or long) would be welcome

Finally, assuming there's interest, we'll head out somewhere for a dinner afterward.

Neuroscientists embrace continuous integration served by Jenkins

Guest post by Yury V. Zaytsev and Abigail Morrison. To download the PDF file of the journal article mentioned below, click here!

As recently exemplified by several reports on this blog, automation tools such as continuous integration servers, that help to defuse the exploding complexity of software under the ever-increasing pressure to deliver, are steadily gaining well-deserved mindshare in the industry.

However, it is not just developers of enterprise software who need solutions to the complexity problem. Scientists are arguably even worse off: most of them are not trained as software engineers, yet, in the last decades, creating custom software has become an integral part of virtually any research activity, be it data analysis, simulation or experiments. Frequently, there is a great emphasis on numerical accuracy and reproducibility of results, which requires extensive testing. As a coup de grâce, most publicly funded research projects are running on tight budgets, excluding the possibility of hiring professional contractors to outsource required software development work.

Enter Jenkins the Butler!

Coming to GDC? Join us for a Jenkins Drink-Up at 21st Amendment

If you are coming to Game Developers Conference in the week of 25th, or if you are local to San Francisco bay area, come join us to the small drink up in the evening of 26th at 21st amendment.

If you are coming, please RSVP so that we know how many to expect, and we can stay connected.

Jenkins CI: The Origins of Butlers, Build Masters and Bowties

The folks at Rebel Labs picked Jenkins as the last installation of their technical report series. It is a beautifully crafted 50 page PDF that covers the overview of the technology. You get to see a bit of details about how ZeroTurnaround uses Jenkins, and it contains a section where I get interviewed by them.

Also, while they failed to mention this in the document, you can use JRebel when developing Jenkins plugins and it'll reduce the # of times you need to restart the VM. To the extent that you use it to develop open-source Jenkins plugins, you can apply for a free OSS license, too.

If that sounds interesting enough, you can get your copy now. Be forewarned that a registration is required.

Jenkins hits 1.500

The last week the Jenkins project has reached a miletone release — Version 1.500. That's no 1.5 nor 1.5.0. That's the 501st release since its inception, counting all the way up from 1.0, 1.1 to 1.500.

We'll be celebrating this release in the upcoming FOSDEM conference in Brussels, but I wanted to thank everyone for making this great community possible by participating and using it.

Despite all the distances we've thus far come, there are still a lot of work to be done, both in the core and plugins, so we look forward to keep on keeping on in the coming years.

So here is to the next 500 release!