Kohsuke wrote the majority of the Jenkins core single-handedly. Kohsuke has more than 10 years of extensive software development experience, ranging from Java to C++, .NET to x64 assembly, as well as systems expertise on several platforms, including Windows, Linux and Solaris. This broad range of experience was a key enabler in the development of various advanced features of Jenkins. Kohsuke is now CTO at CloudBees and an active member of the Jenkins User Conference Governance Committee.
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.
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 (CD), 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!
Discuss the experience of using Jenkins to manage the full stack integration build and testing for DealerTrack 2.0 for 6+ distributed scrum teams. Topics include:
Jenkins master-slave strategy
Hot-fixes vs. development build
Vagrant for isolated build environment
Fabric for deployment
Robotframework-Selenium for acceptance test
Best practices for build, such as test data setup strategy
Jenkins API is a Python module that accesses Jenkins resources and configuring jobs. It combines Jenkins REST and API. In this talk we will demonstrate how to use this module by creating, configuring and triggering a job and seeing the results. We will also talk about adding and deleting a slave. This module helps us to automate scripts which require a Jenkins intervention.
Come to our show where we talk about what CloudBees sees as challenges of deploying, operating, and using large-scale Jenkins installations, and what we are doing to help those users succeed; we'll talk about Jenkins in the continuous delivery era and our efforts in this space, such as Chef/Puppet deployment tracking and workflow. We'll talk about our innovations in DEV@cloud, our hosted Jenkins, and how we bring its goodness to your Jenkins on premise. And last but not least, we'll demo how Jenkins Operations by CloudBees helps organizations scale Jenkins horizontally.
Ever wished that you could fully automate your Integration, Tests and Delivery process for Node.js? In this talk we will demonstrate the full flow of dev, texts and distribution of your Node.js code to your production servers, without losing control. Keep building your extremely flexible Node.js apps made of many NPM without a sweat! And verify that all is good before it hits the production server.
We have used the power of Jenkins to build our Symfony2 Application, send a message using RabbitMQ to a consumer in the app ready to re-deploy itself. Jenkins builds are triggered by creating and accepting merge requests inside of GitLab. Jenkins, GitLab and the app are all deployed in Digital Ocean.
Jenkins CI provides a robust framework for the integration and standardization of scientific workflows. We use Jenkins CI in combination with CellProfiler, an open source image processing software, to build an integrated platform for processing microscopy images and associated data generated from high content screening (HCS). The platform enables scientists to easily access required high performance computing resources, collaborate with each other and easily track data and meta to enhance reproducible research.
More information is a good thing. Normally parameterized build input such as notes, Git branches, and bug tracking issues are lost once a build has completed. The only historical reference is in a report. Consequently, this data cannot easily be reused for future builds. Using Jenkins, Groovy and MySQL, this data can persist for the life of a project. This presentation with describe the simple steps taken to save this information for posterity.
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 can 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 session will discuss two key components of our deployment pipeline: Continuous integration of Chef code and automated deployment of Java applications. CI jobs for Chef code run static analysis and then provision, configure and test EC2 instances. Release jobs publish new cookbook versions to the Chef server. Deployment jobs identify target EC2 and VMware nodes and orchestrate Chef client runs. The flexibility of Jenkins is essential to our overall delivery architecture.
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: 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 on your Jenkins installation/optimization. If you have a specific problem or question, bring it along for our Q&A board!
Lessons learned from running Jenkins for five days with no prior knowledge. Jenkins allows for many different configurations and plugins for building a test automation pipeline, however design, source control of Jenkins artifacts, parametrization to eliminate duplication are key elements to ensure scalability is executed through a new pipeline upon product build availability. These best practices will get you there in less than five days.
At MEDITECH, we needed a way to get individual files from a code base with 260 million lines of source code to build after a commit. This talk is about the issues we encountered, and how we eventually succeeded.
Every enterprise customer engagement is unique and time-sensitive, so it's imperative that a CI tool is flexible, powerful and customizable enough to handle each unique project -- quickly. Learn how we leverage Jenkins to build enterprise-scale WebSphere Portal application components with tools including Subversion, Ant and Maven
Continuous delivery helps you release more, more often, for less. This year it's high on the C-Level agenda and so it should be - it's a game changer for IT. The journey for enterprises to adopt and embed continuous delivery practices into their organization is fraught with peril, but fortunately Jenkins paves the way. To help you ascend your stairway to continuous delivery heaven, here are ten tips for using Jenkins to line up your developers, operations teams, processes and tools. Make sure you don't trip! Come learn the most important considerations as you embark on your first step.