We have some exciting news to share with you! We have finalized most of the dates and locations for the 2015 Jenkins User Conference (JUC) World Tour.
Save the date(s):
- US East (Washington DC): June 18-19
- Europe (London): June 23-24
- Israel: July 16 (ETA)
- US West (Santa Clara): September 3-4
The big news? The JUC agenda has been expanded this year to cover two days! That means you get twice as many opportunities to learn how others are using Jenkins and to network with other Jenkins users.
We need JUC speakers! The Call for Papers is open now and you can apply here. This is an opportunity for YOU to give back to the community by sharing your Jenkins knowledge and success. Jenkins speakers contribute significantly to the overall JUC experience.
In return for speaking, you will receive free admission to the conference and fame/fortune within the Jenkins community. OK, we can’t guarantee the latter, but we can guarantee the former! Hurry and apply now, because the Call for Papers deadline for US East and Europe expires on March 22, 2015.
Not interested in speaking? Another way to contribute to the community is by letting us know who you want to hear from. Nominate or refer that amazing speaker and we’ll do the rest. Contact email@example.com
Lastly, be a JUC sponsor. Any organization can do this – whether a vendor that sells into the Jenkins ecosystem or a company that has received value from Jenkins and wants to give back to the community. You can find out more here. (NOTE: JUC is not a moneymaking venture for the community – so sponsorships do make a difference.)
As a part of the Jenkins 100K celebration, Dean Yu, Andrew Bayer, R. Tyler Croy, Chris Orr, and myself got together late Tuesday evening to go over the history of the project, how big the community was back then, how we grow, where we are now, and maybe a bit about future.
We got carried away and the recording became longer than we all planned. But it has some nice sound bites, back stage stories, and stuff even some of us didn't know about! I hope you'll enjoy it. The MP3 file is here, or you can use your favorite podcast app and subscribe to http://jenkins-ci.org/podcast.
In preparation for Jenkins 100K celebration, I'm going to record a one-time podcast with Dean Yu, Andrew Bayer, and R. Tyler Croy.
My current plan is to go over the history of the project, how big the community was back then, how we grow, where we are now, and maybe a bit about future.
But if you have any other suggestions/questions that you'd like us to discuss, you have 3 or 4 more hours to send in that suggestion! Your feedback would help us make a better recording, so please don't hesitate to tell us.
In preparation of the celebration of 100K installations, 1000 plugins, and 10 years of Jenkins, we've got these images created.
I hope folks can use these images to mark the occasion! The full size pictures are here.
Congratulations! The Jenkins project officially went over the 100K active users mark sometime in January. As of January 31, we were at 102,992. YOU are one of the 100K active users!
As discussed on a couple recent project meetings, we have designated February 26 as Jenkins Celebration Day.
To make some noise, here is what we are doing starting NOW:
- Write a blog about anything related to Jenkins. Post your blog and Tweet out a link to it. Include the hashtag #Jenkins100K in your post.
- On February 26, we will hold a raffle and pick four names at random. The grand prize winner will get a 3D Jenkins Butler model. Five others will get their pick of Jenkins swag (up to $20) from the Jenkins online store.
There are a number of other things planned and we want YOU to be involved. This blog post is the central place to come for all things related to the celebration.
- Recording – Jenkins Governance Board Dean, Tyler, Andrew and I will get together this month and record some thoughts about the Jenkins project. We will share that recording with you from this page on February 26.
- Twitter Badge For those of us on social media that want to proudly celebrate our community, we will have a special badge that you can use for your profile image on Twitter or any of the other social media forums. Feel free to use the badge as long as you want – but let’s get as many of us using it as possible between now and February 27.
Social Media Images
- CloudBees is donating a series of images that we can all push out on social media (whatever platform(s) you use).
- Pick your favorite(s) and push them out on Twitter, Facebook, G+
- Certificate (available on this blog post soon) Download your very own “I am part of the Jenkins 100K” certificate. Print it out and proudly display it on the wall of your cube or office.
- Visibility The Community will also issue a press release on February 26 announcing our milestone news.
- Sign the “card” Consider this blog a Congratulations card to the entire community. Share your thoughts in a comment on this blog about anything Jenkins-related that you wish!
This is a big milestone for the Community and one you should be proud to be part of! Let’s make some noise…
The Jenkins User Conference 2015 is seeking submissions that reflect the latest innovations in Jenkins usage. This is your chance to educate, share and inspire the community with stories of how you've used Jenkins to continuously build that amazing project or how you developed that popular plugin that everyone is using.
If you're gamed, here are some suggestions to get your creative juice going:
- Scaling Jenkins within the enterprise
- Jenkins as the orchestrator for continuous delivery
- Plug-in development
- Jenkins techniques that solve testing/building problems in specific application areas: mobile, enterprise/web/cloud and UI testing
- War stories that speak to a problem you faced, the Jenkins solution you implemented to solve it and the results you realized
- Jenkins best practices, tips and tricks
- Jenkins in the cloud - if you or your company is currently using Jenkins in the cloud we’d love to hear your story
- Beyond Java (Jenkins with PHP, Ruby, etc.)
We are upping the ante at this year's JUCs. We are moving from a 1 day conference to a 2 days conference for SF and London - that's 18 additional cutting edge sessions to be learned.
There's also a wide variety of event sponsorship opportunities available. There are offerings from Gold to Silver packages, exhibitor packages in our world-class expo hall, speaking sessions, free passes, and many branding opportunities. For inquiries, pls contact firstname.lastname@example.org
Looking forward to receiving your amazing proposals!
In tomorrow's Jenkins office hours, Jesse Glick will talk about two topics in the workflow plugin that he has been asked about:
- Security model: script security, permissions
- Plugin compatibility: SimpleBuildStep and friends, custom steps, etc.
The session should be interesting to anyone using workflow or thinking about using workflow. Jesse is one of the top contributors in the community, so it'd be definitely worth your time!
A lot of us has grown fond of our loyal butler Mr.Jenkins over time, which was created by Frontside and chosen as a result of a logo contest. In the true open-source style, the logo has since evolved into many different derivative works, such as a plugin, a 3D model, and a bobble head.
Our friends at CloudBees are running a #BreakingBuilds social media contest through Jan 5th to have some fun with Mr.Jenkins. Read Sacha Labourey's blog post, where he draws parallels between what a butler does and what continuous delivery can do.
I especially agree with him on this point: I always loved the idea of using a butler to represent what Jenkins is about, as it projects all of the qualities that define continuous delivery: it is built to be proactive, it will help you fix problems before they happen, it orchestrates your entire pipeline to production without you having to worry about the sophisticated underlying sequence of steps and, if things go wrong Jenkins uses his fingerprint database to trace back the source of the issue. Full service. As your right arm, Jenkins is the reliable and trustworthy guy you want on your team!
Check out the contest rules and participate. Let's raise the visibility of Jenkins and have some fun in the process!
Jenkins started with a notion of jobs and builds at heart. One script is one job, and as you repeatedly execute jobs, it creates builds as records. As the use case of Jenkins gets more sophisticated, people started combining jobs to orchestrate ever more complex activities.
A number of plugins have been developed to enable all sorts of different ways to compose jobs, and many are used quite successfully in production. But this resulted in a certain degree of complexity for users to figure out how to assemble these plugins.
So we felt the need to develop a single unified solution that subsumes all these different ways to orchestrate activities that may span across multiple build slaves, code repositories, etc. Various inputs from users as well as other plugin developers played a key role.
The result of this is the workflow plugin, which is what a number of us, including Jesse Glick an myself, are focused on in the past few months.
The plugin approaches the problem by defining a DSL for you to describe an execution of a job. Various convenient primitives are available, such as executing shell scripts, checking out the source code, obtaining an executor or a build workspace, etc. All sorts of classic existing plugins contribute their functionalities into this DSL, such as recording test results, fingerprints, or calling into other existing jobs. This allows you to leverage higher-level functionalities and report comprehension capability into a workflow. Similarly, you can leverage the ability of Groovy, the host language of workflow DSL, to define control flows, abstractions, and reuse.
A key feature of a workflow execution is that it's suspendable. That is, while the workflow is running your script, you can shut down Jenkins or lose a connectivity to a slave. When it comes back, Jenkins will still remember what it was doing, and your workflow script resumes execution as if it was never interrupted. A technique known as the "continuation-passing style" execution plays a key role in achieving this.
I'm very happy to report that the workflow plugin is finally 1.0. This version runs on the latest 1.580-based LTS. and we created a docker image for you to play with too. There’s also a JUC presentation that explains this. We are working toward 1.0 release within this year, and in the meantime, the syntax is stable enough to allow you to start designing workflows today.
We've been hearing a lot of good feedbacks and enthusiasm for this new effort. Please let us know what you think.