Jenkins Blogs

In production code, common coding standards for Java recommend writing method names in CamelCase. retrieveUserDetails() createABankAccount() This makes sense when those methods are called from our own code. It feels as if requests are being made to these objects (dear … Continue reading →

Your favorite Butler will visit Israel on June 6 for the Jenkins User Conference Israel. More than 200 people have already registered to hobnob with other Jenkins users and eat like kings.

The agenda is up here. You’ll find a great list of speakers from Israel, Europe and the US to compliment a plethora of treats. There will be an ice cream break, fruits break, beer break and special chef lunch. And everyone gets a limited-edition JUC Israel t-shirt, designed by the t-shirt-design gurus at JFrog.

Featured speakers:

Kohsuke Kawaguchi, the creator of Jenkins (formerly, Hudson) and elite architect at CloudBees, will deliver a keynote about the current state and the future roadmap of Jenkins.

Hans Dockter, the creator of Gradle and the founder of Gradleware will speak about next generation build tool to CI server integration.

Fred Simon, JFrog's co-founder and Chef architect will share JFrog's vision of the future of continous integration in the cloud.

Many thanks to lead sponsors JFrog and CloudBees, who have put a lot of time and energy into organizing the conference. Thanks also to sponsors Cloudify and White Source for showing their support for Jenkins!

Register here.

Can't make it to Israel? Here are more Jenkins events:

• Moving to Continuous Delivery in the Enterprise – June 10, London
• Jenkins Meetup – June 15, Munich
• Jenkins User Event – September 6, Copenhagen
• Jenkins User Conference – October 23, Palo Alto, CA

Volume 4 of Continuous Information came out last night. It contains insights and highlights from founder Kohsuke, the latest growth stats, upcoming event info, Jenkins resources, and more.

Highlights:

• Jenkins has nearly 20,000 more active installations than it had last June, up from 43,500 to more than 61,000
• Nearly 100 plugins have been added since late last Fall when we did the last Jenkins survey. Now there are more than 730 plugins
• Bay Area JUC (Oct 23), JUC Israel (Jun 6) and several other Jenkins events around the world have open registration
• Latest, greatest Jenkins improvements include a new LTS based on 1.509, more context menu improvements, and master/slave data transfer performance improvement
• There's also a Security advisory out recommending upgrade to at least 1.502
• A plethora of Jenkins and Continuous Delivery resources

View the full newsletter, and then sign up to receive it yourself.

And if you have content to feature in a future newsletter, please email us.

With more than 600 plugins, Jenkins has a vibrant community and we're dependent on YOU to keep it that way. Here are 3 ways you can give back to the community to ensure that everyone benefits and Jenkins keeps growing...

Giving it back to the community #1: vendor+community=win

Jenkins is becoming ubiquitous enough that tool vendors and service providers often find their users asking them to provide Jenkins plugins. The challenge for these companies is that they don’t necessarily possess the necessary Jenkins expertise to do one.

Here at the Jenkins project, what we are trying to do is to work with these people to deliver a plugin. It gets the job done a whole lot more quickly if the vendor brings in their expertise on their tool/services and we bring in our expertise on Jenkins plugin development.

For example, we recently worked with SOASTA to help them open-source the plugin they developed in house, then help them add a whole bunch of new functionalities. By open-sourcing a plugin in the Jenkins project, vendors win as the community helps fix bugs and improve plugins. The Jenkins project wins by building relationship with vendors. And finally the users win by having more integrations.

So the next time you ask your vendor to provide a Jenkins integration, please tell them to drop us a note, and we are happy to talk.

Giving it back to the community #2: scratch your itch and take credit

If you are working for a company and hacking some Jenkins plugins for your team, then you should definitely consider contributing those changes back. Let’s take Robert and Tomas for example, who contributed a number of significant plugins from Sony Mobile.

• The company wins, because it shows off their technical excellence. Plus the flexibility to let engineers work on these OSS projects helps them retain and attract high-caliber developers. It also lets the community shoulder some of the burdens of maintaining plugins.
• You win, because now you have more things to show to future employers. After all, GitHub is your new resume! And when you aren’t sure how to go about implementing a feature or fixing a bug, open-sourcing your plugin lets us jump in and get you unstuck.
• The community wins, thanks to your new awesome plugin.
• Besides all of those pragmatic reasons, when you share something with others and they tell you how much it helped them, even if it’s just one or two people, it’s a deeply moving experience.

It just has so many advantages, it’s a no brainer!

Giving it back to the community #3: contribute by proxy

If you are working for a company, wanting to see particular features/integrations in Jenkins but don’t have time to do it yourself, there’s yet another way, and that’s to contribute by proxy.

The idea is that you contract with those who already know how to develop Jenkins plugins, and you have them produce/improve Jenkins plugins in open-source. Praqma is a great example of one such company. They are well connected in the community, with lots of experience under their belts, and your company takes the credit for the work. There are also a number of individuals who can do this for you.

Why give it away something for free when you paid for it, you might ask. That’s because the code sitting in house rots when it’s not maintained by anybody. In contrast, when the rest of the world can hack on your code, you get occasional random bug fixes by strangers (the worst case), and sometimes it gets its own life (the best case.)

If this way of giving back suits you better, feel free to send an e-mail to the dev list.

This year, the West Coast Jenkins User Conference will be in Palo Alto rather than San Francisco. If you’re nearby – or even if you’re not – join Kohsuke and other fellow developers for a solid day of Jenkins.

• The Date: Wednesday, October 23, 2013
• The Venue: Palo Alto Jewish Community Center
• Details
• Register

The Call for Papers is open until June 9 (scroll to bottom of page for form). JUC will be much better with your involvement, so please submit your abstracts and share your Jenkins knowledge with the community.

A very special thanks to our JUC Palo Alto sponsors, who will make sure you are fed, caffeinated, clothed (in this year’s collectible Jenkins tshirt), and generally well cared for at the conference: CloudBees, JFrog, XebiaLabs, appvance, ZeroTurnaround, LMIT Software, Black Diamond Software, New Relic, Liferay, AppDynamics, and SOASTA.

Two other differences this year – the conference is not timed to coincide with JavaOne, and it falls on a Wednesday rather than a Sunday. We thought we’d try these changes and are interested to know if they work better for everyone.

The agenda won’t be populated until after the Call for Papers closes and talks are selected. But you can check out previous JUC agendas, slides, and video:

• 2012 JUC San Francisco
• Inaugural JUC San Francisco - 2011

If JUC Palo Alto is not convenient for you, there’s also a JUC coming up in Herzelia, Israel on June 6 and a Jenkins event planned for Copenhagen, Denmark on September 6.

Hope you can join us at JUC!

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.

If you are interested in coming, please RSVP at meetup.com so that we can prepare accordingly.

You can see your Jenkins build history and re-deploy the older APKs from your Mobile Phone !

This is particularly useful when you want to have multiple of version of your Mobile App to your QA or Beta Testers (just like you !) without having to redeploy or notify anyone: you can go back and forth in a time-machine as many times you want !

Jenkins acts like a APK binary repository with full access to:

• Code changes
• Unit-test executions
• Console output

Join JenkinsMobi V4 Beta now and give your feedback today.

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!

Back in 2011, Yury V. Zaytsev, a doctoral candidate now working at Jülich Research Center, Germany was supported by a Google Summer of Code stipend to design a continuous integration infrastructure for NEST, a spiking neuronal network simulator for neuroscientific research released under the GPL license. An overwhelmingly positive experience with this new setup motivated him to write up a case study, which was recently published in "Frontiers in Neuroinformatics", an open access scientific journal.

"The new CI system boosts our productivity, because it helps us find and fix breakages very quickly, even when they only occur for obscure combinations of configuration options. Automated integration testing is a major breakthrough for NEST, as it ensures that developing new features does not come at the cost of reliability or accuracy" - said Markus Diesmann, director of the Institute of Neuroscience and Medicine (INM-6) at the Jülich Research Center, Germany and NEST Initiative board member.

We hope that through a peer-reviewed publication in a prominent scientific journal we will be able to reach the scientific community more efficiently, as compared to the materials targeting professional software developers. However, we likewise believe that our case study might be of interest to the readers of this blog, especially those who are still only considering implementing continuous integration.

Lastly, we would like to thank all developers and users of Jenkins whose contributions throughout the years made it the versatile and robust continuous integration server it is today!

JenkinsMobi V4 Beta program continues with the support of Assembla SSO Login.

Assembla.com is Cloud ALM that provides Project Workspaces, featuring project management software elements such as task management, issue tracking, cardwall (Kanban), agile project management, Git/Svn  repositories and scrum meetings.

When you configure Jenkins with Assembla Auth Plugin the Jenkins Login process goes through the Assembla SSO Form-based login: this is now automatically managed by JenkinsMobi V4 Beta.

As usual, everything is plug&play: just enter your Assembla Credentials in the JenkinsMobi settings … and then play with JenkinsMobi V4 Beta !

Reblogged from GitEnterprise:

GerritForge is proud to organise the first European Gerrit Code Review Hackathon in London (UK) for three days: 7th, 8th and 9th of May 2013.
The Hackathon is a great way to have the core Gerrit developer Team working side-by-side on some new exciting new features for the OpenSource community. Some of the major improvements in Gerrit architecture and functionality came out from past Hackathons.

Read more… 23 more words

Keep calm and Gerrit Code Review Hackathon

When you configure Jenkins with OpenID SSO, the authentication phase goes through an external web-site (GitHub, Google or others) for authenticating your credentials: when authentication succeded, Jenkins gives you a Session-ID to continue using the API until the session expires.

From JenkinsMobi V4.6.1 (see how to upgrade from JenkinsMobi home screen) you can even automatically manage a 2-step SSO Authentication with your Google Account and Google Authenticator.

1. Edit your JenkinsMobi settings and put your Jenkins URL and SSO username and password.
2. Whenever your Google SSO request a 2-step authentication, you will see a pop-up asking to enter your one-time verification code
3. Tap on “Auth App” to jump directly to Google Authenticator
4. Read the verification code and tap on the “back” button of your Android phone
5. Enter the verification code and tap Verify
6. JenkinsMobi contacts Google SSO and enters again your SSO credentials and one-time verfication code

Your authenticated session will last for the time-to-live of Jenkins Session: should the session be disconnected, you would need to go through the Google SSO and 2-step verification again.

Enjoy JenkinsMobi with Google Authenticator securely over the Internet

 

 

Thanks to the first feedback of the JenkinsMobi V4 Beta, today we have certified JenkinsMobi with OpenID: you don’t have to do anything, just insert your OpenID credentials in the JenkinsMobi V4 settings and, if you have Jenkins-OpenID SSO, everything will magically works

 

JenkinsMobi V4 Beta program is officially started ! 

Follow the the four simple steps described at http://jenkins-ci.mobi/#v4beta and starting exploring the new possibility and provide your feedback on the new JenkinsMobi V4 Architecture.

File encoding is notoriously a difficult problem for developers to fully grok. Development environments and IDEs do not always help. I recently had a test failing under Eclipse, whereas the same test was passing fine in the command line using … Continue reading →

JenkinsMobi v4 has been showcased in Wasaw yesterday, during the 33rd Degree Conference for Java Developers.

SmartPhones and Tablets have revolutionised the way we think, write and use software: software development on Mobile has and need to be agile … but how can you make one step further and have actually your SmartPhone to drive your development ?

Thanks to Jenkins, can Mobile App development and Continuous Delivery be pushed to the edges?

See how you can follow every step of your development with your SmartPhone end-to-end:

• Continuous Integration and Delivery with Jenkins
• Beta notification and distribution to all Mobile stakeholders
• Test execution
• Issue tracking
• Production monitoring

This is a new dimension for the Jenkins eco-system: you will be able to write your plugins to do even more to shorted your continuous application development, testing and deployment.

Beta testing will start shortly … stay tuned

 

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.

JenkinsMobi v4 is the Mobile Engine that powers the 33rd Degree Conference !

The long wait is over … JenkinsMobi has been completely rewritten and will be officially launched next week, 13-15 March  during the 33rd Degree Conference for Java Developers in Warsaw PL.

We will show the new architecture of JenkinsMobi, designed to completely revolutionize the way to organise your Mobile Application Development lifecycle, from the Continuous Integration to Deployment, QA and management of your Production instances in the Cloud.

Follow the JenkinsMobi v4 talk and change the way you manage your Mobile Apps from TODAY !

JenkinsMobi v4 is available for preview as the official App of the 33rd Degree Conference: DOWNLOAD NOW at  or scan the following QR Code.

JenkinsMobi is back !