Submitted by kohsuke on Mon, 2012-07-23 09:00
I'm back from the latest Jenkins User Conference in Israel, and I had such a fun (except the part where I strained my lower back on the day I head back to home so 10+5 hour flights were a torture.) I have this impression that Israeli people form a close-knit community on their own (somewhat like Japanese people do), perhaps because of the difference in the language or the culture. One of the great things about those communities are that people are well connected, and so reaching the right ears and spreading the ideas are easier. JUC Israel turns out to be the biggets JUC we had this year. Shlomi told me that some 230 people registered and 240 people showed up, and this negative last-minute cancellation ratio is unheard of! We had booths from sponsors, 2 concurrent tracks of technical talks, and wonderful Israeli food, in a nice hotel by the beach.
For me, the conference started the night before, when JFrog folks took us to the Hudson restaurant, which was a wonderful steak house. Needless to say I took a lot of pictures. Hudson was great, and I got a wet-wipe in the end to wipe my hands off with Hudson.
Submitted by rtyler on Fri, 2012-06-22 05:00
[ Editor's Note: This was originally posted to the jenkinsci-users mailing list by community member Bue Petersen ]
Praqma inviterer til Gå-Hjem-Møde i Allerød, onsdag d 27. juni kl 17:00. Få en introduktion og demo af Jenkins CI server (Open Source). Vi byder på pizza og en kold øl eller vand. Arrangement er gratis, tilmelding er nødvendig.
Continuous Integration – er et princip der dikterer, at alle ændringer skal integreres, i det øjeblik de er skabt – kontinuerligt og automatisk. Continous Software Validation går skridtet videre - alle ændringer skal valideres, i det øjeblik de er skabt.
Jenkins Continuous Integration Server hurtigt blevet de facto standard for Continuous Integration. Og den er hjørnestenen i build- og softwarevaliderings-systemet og bindeledet mellem samtlige tools i hele den tool-chain, man ønsker at indføre eller udbygge.
På Jenkins konfigureres jobs, som udover at bygge og eksekvere unittests også kan tage ansvar for valideringer som statisk kodeanalyse, rapportering af warnings, coverage-målinger af unittests, automatisk generering af dokumentation, eksekvering af funktionelle tests etc.
Vi holder et uformelt gå-hjem-møde med pizza, øl og sodavand, hvor vi præsenterer Jenkins Continuous Integration og viser dig, hvordan du nemt kommer i gang, så du allerede dagen efter kan høste synlige fordele på dine projekter.
Du kan få helt ny viden og indsigt i din kodebase, og du kan skabe grundlag for ændring af arbejdsgange i udviklingen.
Onsdag 27. juni 2012 kl. 17.00 - 18.30
Praqma A/S
Allerød Stationsvej 4
3450 Allerød
Denmark
Tilmelding
[ Editor's Note: The following is a post from Jenkins CIA member Bruno P. Kinoshita ]
Jenkins will be represented at this years Bioinformatics Open Source Conference (BOSC 2012) on July 13-14th in Long Beach, California. I will be talking about Jenkins during my talk about BioUno.
BOSC 2012 will be held just before ISMB 2012, while registration is through ISMB you don't have to register for ISMB in order to register for BOSC.
I will be at the event with some Jenkins stickers and available to answer questions you might have about BioUno and Jenkins!
About BioUno
BioUno is a project that uses Jenkins as basis for building
biology workflows.
BioUno provides an alternative update center with custom plug-ins for
bioinformatics tools like
MrBayes,
Structure,
Figtree,
Beast,
among others.
While the actual task of analysing or displaying data is handled by specific
tools, that are wrapped by plug-ins, Jenkins is responsible for user control,
web interface, notifications, distributed execution, job schedule and
management, as well as other important low level tasks.
BioUno is similar to BioHPC,
Galaxy and
Taverna, in that all these tools enable creating and managing pipelines using different bioinformatics tools.
However, as it is using Jenkins, BioUno has the advantage of having an Open Source community of hackers that can answer questions and provide assistance for creating new plug-ins. There is plenty documentation for extending Jenkins
and troubleshooting issues, as well as plenty existing plug-ins (that can be used as reference while writing new plug-ins).
There are projects and plug-ins that enable Jenkins to use resources in clouds or turn Jenkins into a Hadoop node, for big data processing. The next steps of the project include the deployment of BioUno to a computer facility, basic infrastructure for BioUno, definition of the process for releasing plug-ins, the creation of more plug-ins and a study on how to handle large data structures, used by many bioinformatics tools.
The project is being developed by TupiLabs under MIT License, and contributions and new plug-ins are welcome.
[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 :
- Comment relire les chapitres ?
- Comment faire part de mes corrections ? Deux solutions :
Si vous êtes intéressé, mais que vous avez des questions, surtout n'hésitez pas à les poser.
On vous attend ! :-)
Editor's Note: The following is a write-up courtesy of Jesse Farinacci
This past week I had the pleasure of attending the Jenkins User Conference in NYC. A hundred other like-minded continuous integration enthusiasts and I packed a very posh Marriott Marquis for a full day of Jenkins excitement.
Famed Hudson and Jenkins founder Kohsuke Kawaguchi delivered the opening address to a crowded room.
I'm sure everyone knows the statistics by now, that Jenkins adoption and development continues at an unbridled pace. Pushing past all the mailing list users and posts, the JIRAs opening and closing, the Twitter followers, the five Jenkins User Conferences scheduled for this year, the unprecedented number of installations reporting anonymous usage, the native availability for nine different OSes, in pushing past all of that..
For me, the most impressive number was that on average there was about 1 plugin created every day over the past year. Let me reiterate that: 1 plugin created every day for a year. If that isn't the best testament to the versatility, extensibility, and just plain usefulness of a piece of software, then I don't know what would be!
Announced at the conference was the general availability of CloudBees BuildHive, this is a mechanism for quickly and easily obtaining access to cloud-based Jenkins. If you have projects on GitHub, you can effortlessly log in to BuildHive via GitHub OAuth, import your projects with literally a single click, and start benefiting from the powerful promise of the cloud. You'll no longer have to worry about managing infrastructure, you'll just get all that great Jenkins CI capability for your projects immediately.
