Join us for an evening of networking, collaboration and discussion at the CloudBees office in Raleigh! Learn how to take Jenkins to the next level with two informative sessions, followed by Q&A.



Agenda



6:00 Food, drinks, and catching up



6:45 Session 1: Using Python's JenkinsAPI to Distribute Tests by Alex Gray (ClearCare Online)



7:15 Session 2: Multibranch Pipeline Tips & Tricks by Jesse Glick (CloudBees)



7:45 Q&A with Alex and Jesse



8:30 Finish



Session 1: Using Python's JenkinsAPI to Distribute Tests



In this session, Alex will show us how to programmatically launch builds on GitHub Pull Requests by using the jenkinsapi pip package. The use case is as follows: Someone creates a PR. Jenkins automatically kicks off a job. The job then reads a test data file from that PR. Based on the number of tests in the data file, the job will then launch a number of "worker" builds to run the tests in parallel and collect the results. The job should gracefully handle updates to the PR mid-test (ie the job should kill any builds on the queue, or that are currently building, and gracefully restart the tests).



Session 2: Multibranch Pipeline Tips & Tricks



Many Jenkins 2 users who have played with “Pipeline-as-code” are familiar with the basics of adding a `Jenkinsfile` to their repository (using either “scripted” or the new “declarative” syntax) and having Jenkins use that to run builds, and may even have seen multiple branches or pull requests being built as separate jobs. But a lot of the details are less familiar. How does `checkout scm` differ from just checking out a branch? What is a “merge” vs. “head” build? How do you control when builds are scheduled in response to new branches or commits? What is the trust model for pull requests from external contributors? How are events like webhooks processed and what is the relation to polling? How do you configure build archiving and other job-level settings? Can the build get metadata about the branch or pull request it came from? What are orphaned branches? Come learn how to fine-tune your Jenkins build behavior.



Speakers



Alex Gray (https://www.linkedin.com/in/alexgrayii/) has been the "Jenkins Master" for various companies for the last 6 years. Before moving to North Carolina from Boston, he and his family took a year off to scratch some things off of their bucket lists (canoeing in the North West Territories, backpacking across Thailand, living in France, just to name a few). He now has a 4 year old who loves camping as much as he does.



Jesse Glick (GitHub (https://github.com/jglick), Twitter (https://twitter.com/tyvole)) is a developer at CloudBees, Inc. working on core Pipeline functionality among other things.