"> Jenkins community survey result is in, which shows a number of interesting stats for us developers, such as 82% of people saying their Jenkins is mission critical, or the spread of distributed builds, especially compared to my earlier similar usage analytics. But just as interesting is the free-form answers to questions like "If there was anything you could you change about Jenkins CI, what would it be?", and while the answer is colorful, there are a few common themes that one can easily spot. One of them is "nothing!", which made me feel good, but another is "UI improvement." And incidentally, Domi has started a thread in the Jenkins-users list about this exact topic a week ago. The idea is to brainstorm what kind of concrete improvements people would like to see, then run them through some real user experience designers and decide which ones are good ideas and which ones are not. I find this thread useful — so much so that one of those ideas (always show the "Save" button at the bottom in the config page) is already implemented toward the next release of Jenkins. So if you have some thoughts to share, please chime in on that thread.

"> Our earlier appeal for donation was a drastic boost to our fund-raising drive, (and looking at the twitter reactions, it feels like the Wikipedia parody we put on Jenkins on Jenkins helped spread the words — I guess jokes do work! And I’m happy to report that we’ve successfully raised over $12000 as of today. That’s more than enough to pay off all the current balance and it should keep the project going for quite a while. I’ve assembled the donor list in appreciation. So once again, thanks everyone for their generous support!

+ image:https://upload.wikimedia.org/wikipedia/commons/thumb/5/51/Mcol_money_bag.svg/100px-Mcol_money_bag.svg.png[image] + + + As we approach the holiday season, which is when people start to feel more charitable, at least in the U.S. So I'd like to make one more plea, that the Jenkins project needs your help in link:/donate/[paying its expense], and that we are still about $1000 shy of the goal we need to get to. So if you can, please help us by https://co.clickandpledge.com/advanced/default.aspx?wid=46160[donating to Jenkins via SPI]. + + + Think about all the benefits you are getting from your Jenkins, and think about all the volunteer efforts that went into it. Some help by writing code, some help by answering other users questions, and some help by spreading words about Jenkins. If you've been wanting to contribute to the project but you haven't figured out how, this is one way to do it. + + + As a thank you, I'm writing a special "friend of Jenkins" plugin that I'd like to send out to those who have donated, so that you can show off your support on your Jenkins instance. + + + Once again, please help us reach link:/donate/[our fundraising goal]. + +

+ In 1.430, we added https://wiki.jenkins.io/display/JENKINS/Translation+Assistance+Plugin[the translation assistance plugin] in the hope of increasing the contribution from the community. It's been 3 months, and I've finally took the opportunity to integrate them into Jenkins. + + + The result is pretty amazing. Before this, we had 26 languages, with wildly varying degree of completeness, such as French, Japanese, German, etc. This is still pretty good, but this integration added updates to 40 languages, including 17 brand-new languages, pushing the total up to whopping 43 languages. Among the newly added languages are Arabic (sorry, no right-to-left support yet), Esperanto, Hebrew, as well as large amount of Chinese (both simplified and traditional) and Korean. + + + While working with this, I've also discovered an issue that prevented Jenkins from correctly showing Hebrew, Indonesian, and Yedish localizations. All these changes will be in 1.443. And going forward, I'll be integrating changes more frequently to reduce the delay. + + + So big thank you for everyone who contributed localizations, and please keep them coming! https://wiki.jenkins.io/display/JENKINS/Translation+Assistance+Plugin[Contributing localization is very easy]. If you are interested in more seriously working on localizations, please see https://wiki.jenkins.io/display/JENKINS/Internationalization#Internationalization-Whattranslatorsneedtoknow%2Fdo[this Wiki page] and request the committership in the project. This is yet another way people can contribute to OSS without writing code.

+ image:https://www.cloudbees.com/sites/default/files/imagefield_thumbs/Buggy_Code.png[image,width=129,height=96] + + + As if https://jenkins-ci.org/content/report-bugs-and-win-kindle[getting a Kindle for reporting bugs] and https://jenkins-ci.org/content/jenkins-community-survey[getting an AppleTV for filing a survey] aren't enough, you can also https://www.cloudbees.com/jenkins-community-contests.cb#bugbounty[win an iPad for fixing an issue]. + + + So if you've been thinking about tinkering with https://wiki.jenkins.io/display/JENKINS/GitHub+Repositories[Jenkins code base] but haven't done so yet, this is a great opportunity to get going. There's https://wiki.jenkins.io/display/JENKINS/Extend+Jenkins[documentation about how to get started], and there's https://wiki.jenkins.io/display/JENKINS/Office+Hours[Jenkins Office Hours] and https://jenkins-ci.org/content/chat[IRC channel] if you need some interactive help from existing devs. I think new features, not just bug fixes, would qualify, so long as it's recorded in the issue tracker. And similarly, I think the plugins would qualify, not just core. + + + + Aside from iPad, there's one $50 Amazon gift certificate going out every week, which is almost a steal! So be sure to submit your entry! +

+ https://en.wikipedia.org/wiki/Census[ + image:https://upload.wikimedia.org/wikipedia/commons/thumb/6/6f/Volkstelling_1925_Census.jpg/300px-Volkstelling_1925_Census.jpg[image,height=140] + ] + + + + There's currently https://bit.ly/rYnFy2[a survey running] to get a better sense of our use base. Those inputs help us steer the effort wisely, so we appreciate your taking time to fill it in. The result would be more useful if larger number of people participate, so feel free to encourage others to fill it in as well. + + + In the same spirit of the fundraising drive in NPR, CloudBees is throwing in a "thank you gift" of AppleTV as an added incentive. See https://blog.cloudbees.com/2011/11/take-jenkins-survey.html[their blog post] for more details.

CloudBees is running a 60-days"bring me bugs" contest for the Jenkins project where you may win a Kindle and Amazon gift cards for a bug report you made during the contest period. See the linked site for details about how to enter into the drawing. Greg Moy from Electronic Arts has already won for the first week, but there are more rounds to come. Several years ago Sun did the same thing around GlassFish, and it was useful to drive more participations into the project. Whether or not you were around the last time, don’t forget to participate this time.

+ image:https://upload.wikimedia.org/wikipedia/en/thumb/3/3b/Solaris_OS_logo.svg/220px-Solaris_OS_logo.svg.png[image] + + + Image Packaging System (IPS) is a new package manager Sun has developed for OpenSolaris. While I have my doubts about whether a brand-new package manager was a good way of spending engineering resources, OpenSolaris had a number of very nice features that made it a convincing platform to run Jenkins, thanks to SMF, ZFS, and zones. So I used to produce IPS packages for Jenkins. I lost the ability to do this as I left Oracle and lost access to a Solaris system, but https://www.dev-eth0.de/jenkins-continuous-integration-on-opensolaris/[a recent blog post] renewed my interest. + + + So I'm happy to announce that the Jenkins project has started producing https://ips.jenkins-ci.org/[IPS packages for the releases]. With this addition, the Jenkins project now produces 9 packages on different platforms (10, if you count https://rubygems.org/gems/jenkins-war[Ruby as a separate platform] :-) +