Managing a modern multi-component application in a continuous integration/deployment environment can be very tricky. In this session we will concentrate on two of the aspects - environment setup, showcasing tools like Vagrant, Chef and Puppet for creating and controlling development, testing, staging, production and other environments; and pushing the deliverables through those environments, using tools like Gradle, Jenkins and Artifactory.
Join us and get all the little tips and tricks that will help you rule your development world.
What if I told you Continuous Delivery with Jenkins was the key to innovation? Choose Digital uses Jenkins to automate all of our testing and deployment. But we take Continuous Delivery one step further, and we use it as a basis to foster product innovation:
What if you could turn every customer interaction into a chance to improve the product or the process?
What if Continuous Delivery could make incorporating new technologies easier so that you could benefit from them faster?
What if you could represent your infrastructure as code, adding flexibility that simplifies scaling and makes it easy to test potential new products and functionality directly with users?
Learn how you can use Jenkins to extend the product feedback loop beyond the developer’s den and into the business team and customer’s lair.
This talk provides the tools necessary to debug a Jenkins instance if something happens. For example, what if the Jenkins UI doesn’t work? Or the Jenkins instance is frozen (deadlocked)? I will equip users with the necessary tools and techniques I use as a support engineer to debug these issues and get your instance back to a stable state.
Jenkins at Realm: Best practices for CI in a mobile-oriented company dealing with multiple platforms, requiring multiple programming languages and developed by multiple teams spread around multiple continents.
Jenkins is great. We know it well enough, though, to realize that it’s also not a silver bullet. As we look to move from build and CI to DevOps and Continuous Delivery, there are many other tools in our toolkit that we will need to integrate in order to have effective, flexible automation that supports our teams and initiatives. We will classify and discuss various categories of CD and DevOps tools, highlighting which tools are best used for which tasks. We’ll present an outline of an effective CD toolkit based on allowing best-of-breed tools to do what they do best without overstretching and breaking them. By swapping our hammer for a proper toolkit, not every problem in application delivery need look like a nail!
What plugins, tools and behaviors can help you get the most out of your Jenkins setup without all of the pain? We’ll find out as we go over a set of Jenkins power tools, habits and best practices that will help with any Jenkins setup.
Emerging technologies and processes have led to continuous delivery as the current summit of software development processes, but what might the future hold? Grounded in my own background and current work with continuous delivery, I explore a number of ongoing concepts and new ideas that are evolving out of old and new technologies and how they could shape the course of agile development and release in the years to come.
The last thing Jenkins needs is another Domain Specific Language (DSL); many attempts have been made to surface a DSL for Jenkins, but they have all fallen short of capturing Jenkins’ powerful extensibility. Rather than wheeling out yet another custom DSL, we unmask the true Jenkins DSL that has been hiding under our noses, which captures Jenkins extensibility and works with virtually every plugin, by design.
Jenkins may start small in a company, but it often spreads across departments faster than a virus. And the bigger the installation, the more care you need to take in setting up your Jenkins infrastructure. In this talk, we’ll teach you our top ten best practices that enterprises can use to get the most out of Jenkins. As part of the discussion, we’ll share a few case studies from companies who have implemented Jenkins on a large scale and who are supporting dozens of development teams, hundreds of applications and thousands of builds per month. We’ll also give you our list of top five most useful plugins for your Jenkins installation, and teach you our favorite tips on how to jump-start your Jenkins installation/optimization activities. If you have a specific problem or question, bring it along for our Q&A board!
At eBay we developed a federated model for CI where each developer gets their own Jenkins instance running on a dedicated VM. Only 20% were actually used and even those VMs were utilized less than 25 minutes per day. To solve this we built a highly-available, self-healing cloud infrastructure with Apache Mesos, Marathon and Jenkins. We got more value for each buck spent on resources.
As your Jenkins instances get bigger and numerous, keeping them up & running, performing maintenance operations like restarts & upgrades, and organizing them become more important. These are common problems we at CloudBees see a lot. In this talk, we’ll explain the techniques and toolkits that we’ve developed in this space over time, some of which we are delivering as features of Jenkins Operations Center by CloudBees.
When pushes to production fail, the “blame game” starts between developers and DevOps, then everyone scurries to figure out what really happened…fast! Adam Culp will show how a PHP application can be deployed flawlessly using Jenkins. Then see how “Dev” and “Ops” are both supported by a system if the application breaks and the nightmare happens.
eBay and PayPal have been using Jenkins (and previously Hudson) for a very long time. Right from provisioning CI VMs via Mesos/Dockers, securing CI, pipelines for code propagation etc., Jenkins has enabled us to execute brilliantly on every single aspect of PDLC. In fact, Jenkins is central to our PDLC scheme. We would like to share our journey and usage with the wider Jenkins community. The goal is to share our Jenkins knowledge, usage and advanced configurations.
Netflix has an entire Symbian Army and this is our first “monkey.” The CI Monkey leverages the GitHub Pull Request Builder, Jenkins Job Builder and a shell script to automatically create CI builds. This talk will go into detail on the two technologies used by the CI Monkey, then talk about the CI Monkey itself: what it does and how to use it.
Learn about using CI Monkey to:
Get results of tests or user feedback sooner
See how smaller changesets equals smaller amounts of code to troubleshoot to find a problem
Set up a stepping stone to continuous delivery
Why use CI Monkey? Because you’ll:
Save time and effort creating builds
Avoid missed repos
Be able to change job configuration with the CI Monkey
Utilize GitHub Pull Request Builder
Enable almost automatic CI on a dev branch
GitHub Pull Requests provide a great code review system. However, for non-trivial code changes actually evaluating the system is valuable. I present a way of using the Jenkins GitHub Pull Request Builder and Apache VHosts to automate building out an environment to test a pull request automatically. My pull request test automation was developed for a PHP application.
When people’s lives depend on your software, you want it to be built and tested correctly. Learn how Cerner Corporation, one of the world’s leaders in Healthcare IT, uses Jenkins to build and test some of the most complex software in the world. Also, learn how we leverage Jenkins to use cloud, mobile and desktop platforms for a broader CI process while making the process more efficient and dependable.
Plug real devices into your Jenkins process and automate testing
Join Perfecto Mobile’s discussion and say Yes to extending your CI process to mobile projects.
Yes, you can automatically deploy builds on real devices in every Jenkins build.
Yes, you can perform automated functional testing every build cycle.
Yes, you can shift left with early single user performance profiling.
More than theory, watch Perfecto Mobile demonstrate an end-to-end Jenkins build while pointing out the ‘gotchas’ of automated app testing on real devices executed in parallel.
This session will focus on how my team at Target introduced continuous integration to the company, used Jenkins to solve that undertaking and how adoption went from one team to dozens. I’ll talk about:
The hurdles we faced (people, culture, etc.)
How to sell the benefits to teams
The plugins we use
How we’ve scaled it using Jenkins Enterprise
ROI we have realized
Jenkins has various ways to “chain” projects together: triggers, promotions, copied artifacts, etc. However, assembling these into a complex continuous deployment pipeline can be painful. A new open source job type is under development that lets you use a single, readable Groovy script to orchestrate long-running build processes on one or more slaves. Complex control structures, human interaction and restarting from checkpoints are all within scope. Come hear about this powerful new system and get involved.
In this session, we will look at the Tapjoy Ruby RSpec workflow, from GitHub pull requests received by the ghprb plugin, to the workflow plugin and the ec2 plugin and spot instances as nodes. We automatically build each pull request and update the GitHub UI with results and parallelized builds on the spot. With this process, we have reduced test turnaround from 90 minutes to seven minutes. We use fancy Groovy glue to name builds and link to people and branches. Pretty sweet!