On December 15, the Toulouse JAM was co-hosted with the Toulouse JUG and Toulouse DevOps. Indeed it made sense since Jenkins is written in Java, makes use of Groovy code in many places (system groovy script, job dsl, workflow...), and it also made sense to co-organize with the local DevOps community since Jenkins is also a great tool to enable Continuous Integration, Continuous Delivery and automation in general. There were 103 RSVPs, with 80 to 90 people in attendance.
There were 3 talks planned for the evening:
- Job DSL Intro [fr], by Ghislain Mahieux
- Workflow plugin [fr], by Michaël Pailloncy (co-maintainer of the Build Trigger Badge plugin)
- Feedback on almost 10 years of CI and what's upcoming [fr], demo with Jenkins build scaling with Docker Swarm, by Baptiste Mathus
Note: presentations have been recorded (in french). They are still being processed, and once they are posted we will update this blog.
Thank you to Netflix for sponsoring the yummy burrito bar and offered up their brand new auditorium to host Jenkins Developers and Users Meetup group on Dec 16. We had 96 RSVPs which was impressive. Our speaker for the evening was Akshay Dayal, Software Engineer at Google. Akshay's session was about Scaling Jenkins - how and why Google decided to scale their existing Jenkins cluster (OSS) to meet their security/availability and failover requirements and how heavy automation played an important role in this effort.
The second talk was about how Google worked with Jenkins to read config data externally. Slides are listed below. The video will be posted HERE once it becomes available.
Scaling Jenkins slides can be found HERE
External Project slides can be found HERE.
Although December is a short month due to the holidays, there has been a good amount of local Jenkins activities that took place regardless of holiday obligations. Today and tomorrow I will be doing a series of posts to summarize December JAM World Tour. Special thanks to the JAM organizers and co-organizers who made it all happen in these cities:
On December 9 Lima JAM hosted their first Jenkins meetup in Lima, Peru. There were attendance from various roles of DevOps: Dev, QA, and Ops. There was also a good mixture of different levels of Jenkins users, some were new and just starting to use Jenkins while others had extensive Jenkins experience.
The group has been invited by Docker and Ansible meetup organizers for a joint event in January to showcase technologies from Jenkins, Docker, and Ansible. Congrats to Lima JAM group.
In total there were about 80 attendees at the meetup. In addition to meetup.com the event has been promoted by Yandex so we quickly reached capacity limit.
There were 3 talks conducted, speakers from Yandex, ZeroTurnaround and CloudBees. We discussed the current open-source project state, ongoing activities in the community, Jenkins-powered CD case studies from ZeroTurnaround and Jenkins plugin development approaches.
"Who is Mr. Jenkins? Current State, common usage issues and trends in the community"
"Jenkins beyond CI. ZeroTurnaround's experience"
"When to write your own plugin and when not to"
Jenkins QA Session:
As I mentioned in yesterday's post, we're planning a "Contributor Summit" on February 1st, after FOSDEM 2016 (January 30th/31st), to focus on Jenkins 2.0. Since many of us are already planning, the Monday following the event turned out to be the ideal time to discuss 2.0.
Note: If you're not already familiar with some of the key proposals that were put forth, you can review them in the Jenkins 2.0 proposals summery page.
We've hosted one or two Contributor Summits in the past, and they're usually a day-long event where we try to gather a number of Jenkins core/plugin developers and active/power users to have detailed discussions around the theme of the summit. For this "Jenkins 2.0 Contributor Summit" we do not have a complete agenda yet, but we will post that to the Meetup event once it is fully prepared in the next couple weeks.
Suffice it to say, we'll be discussing a lot!Venue and RSVP
The Contributor Summit will be hosted in a CloudBees office at: Rue des Colonies, 11, Brussels, Belgium. If you're already planning on attending FOSDEM, the office is near Grand Place and Cafe Delerium (where the Friday beer event is hosted).
The venue is of limited size, so if you're planning to join us, please RSVP to the Meetup event as soon as you're certain you will be able to attend. If you find yourself unable to attend, please remove yourself from the list to ensure that we can fit as many active contributors into the office as possible!
While we are gearing up for FOSDEM 2016 early next year in Brussels, I wanted to remind the Jenkins community about our Travel Grant Program. We're a little late on mentioning it, but the board has allocated the money to help Jenkins contributors travel to Brussels to participate in FOSDEM and the Jenkins Contributor Summit which we will be hosting the day after, Feb 1st, which we'll discuss more in a later blog post.
For the FOSDEM Travel Grant Program, we are able to cover up to $500 (USD) in expenses to help community members participate in FOSDEM.
If you're interested, please read the description of the program below. Please note that some of the details of the program are different from the linked grant program page
Regardless we hope to see you all at FOSDEM on January 30th and 31st, 2016, in Brussels!Eligibility
All community members are eligible for support unless they've received a travel grant within the last year (based on the event's date). However, as we have very limited funds to support this program, we'll prefer applications by active contributors to the Jenkins project.
If you have other possible funding sources, please look to them first. This will allow more people to attend a Jenkins community event.Application
The application process for FOSDEM, due to our poor timing, deviates from the traditional Travel Grant Program.
To apply for a travel grant, send an email with the following information to the Governance Board at firstname.lastname@example.org before January 6th.
- Your name
- The event you'd like to attend
- The expected cost of travel (airfare, hotel, conference fees, etc.)
- A description of your contributions to the Jenkins project, such as:
- Plugins you developed
- Pull requests you authored
- Documentation you wrote
- Public presentations on Jenkins-related topics
- Why should we sponsor your trip?
If you've been selected for a travel grant, we'll expect you to:
- Be available for a blog post about this program before the event.
- Help out at the Jenkins stand at FOSDEM
- If your schedule permits, we'd love to see you at the Jenkins 2.0 Contributor Summit the day after FOSDEM.
It should go without saying that we expect all Jenkins contributors representing the project at an event such as FOSDEM to act in a respectful and constructive manner. As we have not yet formally adopted our own Code of Conduct, we recommend reviewing the FOSDEM Code of Conduct.
After the trip, please submit a travel report to email@example.com mailing list. This report should include the following:
- What you accomplished at the event
- What you learned at the event
- Contacts you made
- Other useful information
We also expect you to submit your receipts via email to the person mentioned in the travel grant confirmation for review. We will reimburse actually incurred costs up to the 500 USD limit.
A lot of people are using the Workflow plugin, but as with any scripting environment, users often have to start from scratch and learn the same lessons and shortcuts that other users have already learned. While there are blog posts from developers and users in various places, and some samples in the Workflow plugin documentation, more examples and tips and tricks are always, always useful. To help with that, we've created the workflow-examples repository on GitHub, as a place to store community-developed Workflow scripts that can help new users get started, show how to accomplish some non-trivial goals, and find tips and trick for taking your Workflow pipeline to the next level.
The repository has four directories:
- docs/ - documentation, guides, and more. Including a Best Practices document. We'd love to see more contributions to that doc, as well as any new ones that would be helpful to Workflow users!
- workflow-examples/ - general Workflow examples, showing how to use a given plugin with Workflow, quirks of the Workflow DSL syntax, and more.
- global-library-examples/ - examples of how to write code for the Workflow global library.
- jenkinsfile-examples/ - Sample Jenkinsfiles or other Workflow scripts from SCM .
During Hacksgiving some initial content was added, but not everything is covered yet, which is why I'm posting this - more is needed. We'd love to see your tips, examples, gotchas and more. If you've got Workflow scripts you'd like to contribute, please read the README and send a pull request. Thanks!