Recent Blog Posts

As you may or may not know, the Jenkins project has a bi-weekly IRC meeting where we discuss and decide on things necessary to keep the project running. Next Sunday, we’ll bring this project meeting live to Jenkins User Conference San Francisco. Since this is an unique opportunity to engage people who don’t normally come to these meetings, I’d like to encourage everyone to propose agenda items and add it to the agenda page. The Wiki page lists all the past meetings, so you can get a sense of what it is like. But this time, we hope to have a good number of users to the meeting, not just project insiders. So if you have things you’d like to get users feedback on, or if you like project insiders to update you on things, please don’t hesitate to add them. I still need to work on the logistics, but the plan is to do a cross-over with IRC — I’d like to show the IRC client projected in the room, so that people in the room can see the conversation in IRC, and I’d like either real-time transcribing of voice conversations to IRC and/or live broadcasting of the room.

[ Editor’s Note : The following is a guest post by Jenkins contributor Baptiste Mathus. For the non-French speakers, we’re looking for French speakers to help translate "Jenkins: The Definitive Guide" ] Si vous vous intéressez à Jenkins et que vous aimeriez pouvoir y contribuer, lisez la suite. L’année dernière, en août, nous avons attaqué la traduction en français du Jenkins Definitive Guide, écrit en bonne partie par John Ferguson Smart. Le travail a avancé doucement, mais a avancé tout de même. A ce jour, sur la quinzaine de chapitres, trois sont traduits et relus, et presque tout le reste est en cours. Mais je ne parle pas bien anglais…​ Ce n’est pas grave. Il y a plusieurs chapitres où il faut simplement relire, et donc parler et écrire correctement le français est suffisant. Si éventuellement, vous ne comprenez pas certaines parties traduites, et qu’il faut relire l’original, vous pouvez toujours soulever la question sur la liste de diffusion du projet où on parle français. Je ne suis pas développeur, ou je ne connais pas Git, ou les deux Si vous voulez vous former à Git, c’est l’occasion. On se fera un plaisir de répondre à vos questions sur la liste de diffusion, même si elles sont exclusivement liées à Git, et pas (encore) à la traduction :-). Mais si vous ne le sentez pas ou n’avez pas le temps, ce n’est pas grave. Vous devez simplement savoir éditer un fichier XML. Il y en a un pour chaque chapitre. Super ! Par où je commence alors ? Comment se signaler : Il y a une page wiki qui récapitule l’état de la traduction, chapitre par chapitre. Indiquez votre nom en tant que relecteur, et c’est parti. Si vous le souhaitez, mais ce n’est pas une obligation, vous pouvez vous présenter sur la liste de diffusion du projet. Comment relire les chapitres ? Le plus simple est de lire la version HTML publiée en continu grâce à CloudBees. Comment faire part de mes corrections ? Deux solutions : Git : vous forkez le projet GitHub : Jenkins - Le Guide Complet, vous créez une branche pour la relecture, vous committez vos vos corrections, et vous faites une pull-request. Copiez le fichier XML du chapitre qui vous intéresse à partir de la page du projet puis vous l’envoyez sur la liste de diffusion lorsque vous avez fini. Si vous êtes intéressé, mais que vous avez des questions, surtout n’hésitez pas à les poser. On vous attend ! :-)

"> 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.

+ 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.

A little over a week ago we opened the polls to the larger user-base to vote for the new and improved Jenkins logo. After receiving hundreds of votes, we are now ready to enter the final round of voting (click images to see larger versions in a new window). Voting will end April 9th at 23:59 UTC, so make sure to tell your friends, coworkers and bus drivers to get their votes in as soon as possible! + Logo #1"> + Logo #2"> The Vote If the iframe doesn’t properly load for you, you can open Loading..." class="bare">https://spreadsheets.google.com/viewform?formkey=dEl2T1gwdko1YXBxcktiTEJzUXZleUE6MQ Loading... If you’re interested in the results for the first round, you can find them in this gist

After a number of absolutely fantastic logo submissions from a number of designers, I’m extremely pleased to open the polls on the vote for the brand new Jenkins logo! The thumbnails do not do any of these logos justice in my opinion, so I recommend opening each logo up in its own tab to get the full effect :) I plan to end voting March 28th at 12:01 UTC. The Logos Logo #1 Logo #2 Logo #3 Logo #4 Logo #5 Logo #6 Logo #7 Logo #8 Logo #9 Logo #10 Logo #11 The Vote If the iframe doesn’t properly load for you, you can open Loading..." class="bare">https://spreadsheets.google.com/viewform?formkey=dE9GNlpNbVEwa0VPZHl1TkJCaUI1Z2c6MQ Loading...

Squee-D had some nice things to say in the #hudson IRC channel yesterday that I thought I would share: Just to sing some praise again, make sure you all know how appreciated it is, we absolutely love hudson, and appreciate everyone who develops and maintains it. Positive feedback (and negative really) is always appreciated; have you thanked your plugin maintainer today?