Git Bootcamp - An All-Day Workshop

Matthew McCullough

Tuesday 9:00 AM - Atlantic III

Distributed version control is all the rage these days, but is it worth it? It has been transformative for the dozens of organizations and thousands of developers that I've mentored on the unique implementation called Git. But don't take my word for it. Discover the joy of a version control system that works for you, not against you, in a hands-on workshop. Bring a Windows, Mac, or Linux laptop and we'll install, set up, use and bend Git into workflows that weren't even possible with the version control systems of yesteryear. Be prepared to rethink how lightweight, fast, and refreshing source code control can be. After completing this workshop you'll be able to do practical work with Git for your day job or weekend OSS hobby

This full day workshop takes you from the ground up with Git. By the end of the day you'll be proficient enough to contribute to an open source project using Git or to leverage inside your corporate as the canonical version control system.

Enter The Gradle

Hans Dockter

Wednesday 8:30 AM - Atlantic VI

This presentation introduces the audience to the power of Gradle through many real-world examples that are demonstrated live. By the end of the presentation, you'll understand how Gradle helps to elegantly solve the challenges that we face in our daily enterprise builds.

We'll go through such powerful concepts as: advantages of declarative over imperative build systems, convention over configuration without rigidity, task definitions and dependencies, the benefits of plugins, deep multi-project support, runtime optimizations through partial builds and harvesting existing functionality through Ant and Maven integration as well as strategies for migrating from these build tools. We will demonstrate some of the innovative goodies that come with Gradle out-of-the-box, like smart incremental builds, the Gradle Daemon and the Gradle Wrapper. We show also many of the new features like Eclipse integration, Sonar integration, Heroku integration, C/C++ support and other new plugins.

Hands on Cloud Storage

Adrian Cole

Wednesday 8:30 AM - Atlantic V

You may have heard about cloud storage offerings such as Amazon S3, OpenStack or Microsoft Azure. While conceptually similar, these offerings have different apis and behaviour that place the "write once (run|test) anywhere" mantra at risk. The jclouds open source java and clojure library aims to eliminate cloud vendor lock-in, exposing easy to use, portable, and powerful APIs. Bring your laptop, armed with latest revs of Eclipse, git, and maven, and we'll walk through getting you setup to hack jclouds java or clojure BlobStore applications in a collaborative fashion.

During this workshop, you'll discover the value and key gotchas of cloud storage providers first hand. By the end of this session, you'll be writing testable code that creates and manages containers and blobs, and understand how cloud storage can fit into your architecture.

Continuous Delivery All-day Workshop, Pt. 1: Deployment Pipelines

Neal Ford

Wednesday 8:30 AM - Himarshee

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In this workshop we take the unique approach of moving from release back through testing to development practices, analyzing at each stage how to improve collaboration and increase feedback so as to make the delivery process as fast and efficient as possible. At the heart of the workshop is a pattern called the deployment pipeline, which involves the creation of a living system that models your organization's value stream for delivering software. We spend the first half of the workshop introducing this pattern, and discussing how to incrementally automate the build, test and deployment process, culminating in continuous deployment.

Enter The Gradle

Hans Dockter

Wednesday 10:30 AM - Atlantic VI

This presentation introduces the audience to the power of Gradle through many real-world examples that are demonstrated live. By the end of the presentation, you'll understand how Gradle helps to elegantly solve the challenges that we face in our daily enterprise builds.

We'll go through such powerful concepts as: advantages of declarative over imperative build systems, convention over configuration without rigidity, task definitions and dependencies, the benefits of plugins, deep multi-project support, runtime optimizations through partial builds and harvesting existing functionality through Ant and Maven integration as well as strategies for migrating from these build tools. We will demonstrate some of the innovative goodies that come with Gradle out-of-the-box, like smart incremental builds, the Gradle Daemon and the Gradle Wrapper. We show also many of the new features like Eclipse integration, Sonar integration, Heroku integration, C/C++ support and other new plugins.

Continuous Delivery All-day Workshop, Pt. 1: Deployment Pipelines

Neal Ford

Wednesday 10:30 AM - Himarshee

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In this workshop we take the unique approach of moving from release back through testing to development practices, analyzing at each stage how to improve collaboration and increase feedback so as to make the delivery process as fast and efficient as possible. At the heart of the workshop is a pattern called the deployment pipeline, which involves the creation of a living system that models your organization's value stream for delivering software. We spend the first half of the workshop introducing this pattern, and discussing how to incrementally automate the build, test and deployment process, culminating in continuous deployment.

Hands on Cloud Storage

Adrian Cole

Wednesday 10:30 AM - Atlantic V

You may have heard about cloud storage offerings such as Amazon S3, OpenStack or Microsoft Azure. While conceptually similar, these offerings have different apis and behaviour that place the "write once (run|test) anywhere" mantra at risk. The jclouds open source java and clojure library aims to eliminate cloud vendor lock-in, exposing easy to use, portable, and powerful APIs. Bring your laptop, armed with latest revs of Eclipse, git, and maven, and we'll walk through getting you setup to hack jclouds java or clojure BlobStore applications in a collaborative fashion.

During this workshop, you'll discover the value and key gotchas of cloud storage providers first hand. By the end of this session, you'll be writing testable code that creates and manages containers and blobs, and understand how cloud storage can fit into your architecture.

Continuous Delivery All-day Workshop Pt 2: Agile Infrastructure

Neal Ford

Wednesday 1:30 PM - Himarshee

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In the second half of the workshop, we introduce agile infrastructure, including the use of Puppet to automate the management of testing and production environments. We'll discuss automating data management, including migrations. Development practices that enable incremental development and delivery will be covered at length, including a discussion of why branching is inimical to continuous delivery, and how practices such as branch by abstraction and componentization provide superior alternatives that enable large and distributed teams to deliver incrementally.

Enterprise Gradle

Hans Dockter

Wednesday 1:30 PM - Atlantic VI

In this talk we will cover many Gradle power features that are particularly helpful for the real heavy lifting often needed in enterprise builds.

We will start this session with the concept and advantages of autowiring the Task Dependency Graph based on the inputs and outputs. We will then talk in detail about the new dependency management features such as the new cache, customizable dynamic revision handling and customizable version conflict resolution. From there we'll explore the new extension mechanism for the Gradle DSL and introduce the Gradle daemon. We will also discuss our take on best practices for dealing with module dependencies in the enterprise and how this can be mapped with Gradle. Finally we will show how you can programatically customize the way the Gradle build model is mapped to the STS Gradle Eclipse plugin. All those features are presented in the context of our roadmap and what further improvement you can expect with future releases.

Sonar Half-Day Workshop

Matthew McCullough

Wednesday 1:30 PM - Atlantic V

You've heard about Sonar and are intrigued by its features. It can analyze code in both a static and dynamic manner making aggregated sense of the complex figures gathered by the underlying tools such as CPD, FindBugs, Cobertura, Checkstyle, and many more. You believe your team can benefit from using it to gather metrics and to facilitate code reviews. But how do you get started? The answer is easy. Through a hands on workshop that has you installing, running, and reviewing code.

This workshop is purely hands on and will give attendees first-hand experience of the setup, configuration, and use of Sonar to analyze Java and Groovy code. Attendees will install Maven, Gradle and then Sonar and proceed to analyze an open source project, all during the course of this three hour class.

Sonar Half-Day Workshop

Matthew McCullough

Wednesday 3:15 PM - Atlantic V

You've heard about Sonar and are intrigued by its features. It can analyze code in both a static and dynamic manner making aggregated sense of the complex figures gathered by the underlying tools such as CPD, FindBugs, Cobertura, Checkstyle, and many more. You believe your team can benefit from using it to gather metrics and to facilitate code reviews. But how do you get started? The answer is easy. Through a hands on workshop that has you installing, running, and reviewing code.

This workshop is purely hands on and will give attendees first-hand experience of the setup, configuration, and use of Sonar to analyze Java and Groovy code. Attendees will install Maven, Gradle and then Sonar and proceed to analyze an open source project, all during the course of this three hour class.

Cooking Up Infrastructure with Chef

Matt Stine

Wednesday 3:15 PM - Atlantic VI

Chef is a community-developed platform for automated provisioning, configuration, and integration of software infrastructure. It currently boasts 190+ individuals and 40+ companies (including parent company OpsCode) as contributors, and companies like EngineYard, ElectronicArts, GoTime, and Rhapsody as adopters.

Chef achieves fully automated infrastructure via three primary disciplines:

• Automated provisioning of bare metal, virtualized, and cloud environments
• Configuration of servers via roles ("webserver", "appserver", "loadbalancer") and recipes, which are declarative descriptions of resource (e.g. Apache, MySQL, Hadoop) configurations written in a Ruby DSL
• Systems integration via dynamic lookup and discovery

We'll dive deeply into Chef's architecture and features, including its idempotency, its thick client/thin server philosophy, its intentional lack of dependency management (preferring and order-based configuration), and its deep integration with other tools. We'll then leverage Chef to set up infrastructure of a typical JVM-based web development project with various OS, application server and datastore configurations. You'll leave a ready to get cooking with Chef on your next software delivery effort.

Continuous Delivery All-day Workshop Pt 2: Agile Infrastructure

Neal Ford

Wednesday 3:15 PM - Himarshee

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In the second half of the workshop, we introduce agile infrastructure, including the use of Puppet to automate the management of testing and production environments. We'll discuss automating data management, including migrations. Development practices that enable incremental development and delivery will be covered at length, including a discussion of why branching is inimical to continuous delivery, and how practices such as branch by abstraction and componentization provide superior alternatives that enable large and distributed teams to deliver incrementally.

Master of Puppet

Matt Stine

Wednesday 5:00 PM - Atlantic VI

Puppet is a powerful framework for the automation of tasks typically performed by system administrators as part of software infrastructure provisioning and maintenance. Puppet adoption is rapidly increasing, boasting use by companies such as Google, RedHat, Constant Contact, Zynga, and Shopzilla.

Puppet is composed of three principle components:

• a declarative language for expressing system configuration,
• a client and server for distributing it,
• and a library for realizing the configuration

We'll dive deeply into Puppet's architecture and features, including its idempotent configurations, cross-platform resource abstraction layer, and graph-based modeling of resources, resource providers, and resource relationships. We'll then leverage puppet to set up infrastructure of a typical JVM-based web development project with various OS, application server and datastore configurations. You'll leave a "Master of Puppet," ready to apply it on your next software delivery effort.

Deployment with Capistrano

David Bock

Wednesday 5:00 PM - Himarshee

Capistrano is the de-facto tool used to deploy Rails applications, but it is useful for so much more. In this talk we will publish a real website from scratch, with consideration for real world stuff like safeguarding passwords, turning on and off application monitoring, multiple machine deployments, and general system administration tasks.

In addition to a real deploy in-session, we will look at the real deploy scripts for several real-world, large websites involving multiple machine architectures, minimal (sub second) downtimes, and different server configurations.

Behavior Driven Infrastructure

Jeffrey Hulten

Wednesday 5:00 PM - Atlantic V

Maybe you have used Cucumber (or cuke4duke) to define and test the behaviors of your code, but what about the behaviors of the platform your code is running on. With the push towards 'infrastructure as code' shouldn't we test it as well?

In this session we will walk through defining the behaviors of our system, writing step definitions to test them, and adding those tests to a monitoring system.

Metrics for steering your projects to success

David Bock

Wednesday 8:30 PM - Himarshee

There are a lot of things we can measure about our source code, but what about the "project as a whole" and its overall health? Are there ways of measuring the effectiveness of our processes? Are there things we can measure that would point to project automation wins? Is there a way to measure team 'morale'?

While we can gather a lot of metrics from automated source inspection tools, those can make us focus on the wrong "problems to solve"... There are a lot of personal, team, and project-level things we can measure and tune that can lead to big wins. Using advice from an obsessive-compulsive numbers collector, the Personal Software Process, Scrum, the Pomodoro Time Management Technique, and Personal Kanban, we will discuss ways of effectively measuring aspects of our team and our productivity, and actions we might take based on what we learn.

Java/Groovy Cloud Computing

Brian Sam-Bodden

Thursday 9:00 AM - Himarshee

In this workshop you will learn how to design, develop and deploy Java and Groovy applications on the Cloud. Learn about GAE (Google App Engine) and Amazon EC2 (Elastic Compute Cloud)

In this workshop you will learn how to design, develop and deploy Java and Groovy applications on the Cloud. Learn about GAE (Google App Engine) and Amazon EC2 (Elastic Compute Cloud)

Monitoring What Matters

Jeffrey Hulten

Thursday 9:00 AM - Atlantic VI

"Is it Running Now? Good!" Too often the scope of monitoring is "the server returns 200" or "a string is present" but this is usually a small part of what our web applications do. If you ran Twitter would you want to know the number of tweets per second? If you ran Amazon would you want to know the number of orders per hour?

In this session we will discuss what to measure, how to measure it, and demonstrate using various techniques to expose our measurements to monitoring software.

Java/Groovy Cloud Computing

Brian Sam-Bodden

Thursday 11:00 AM - Himarshee

In this workshop you will learn how to design, develop and deploy Java and Groovy applications on the Cloud. Learn about GAE (Google App Engine) and Amazon EC2 (Elastic Compute Cloud)

In this workshop you will learn how to design, develop and deploy Java and Groovy applications on the Cloud. Learn about GAE (Google App Engine) and Amazon EC2 (Elastic Compute Cloud)

Stop, DevOp, and Roll Out Software

Matt Stine

Thursday 11:00 AM - Atlantic VI

What is the DevOps movement? It a nutshell, it is the idea that the days of silos are over. Development, QA, and operations can no longer be thought of as separate warring divisons with their own "turfs." Instead, we must focus on the fact that we are all part of a single value stream for the customer. By collaboration and shared expertise, we can find real overlaps between our previously segregated areas of expertise and optimize that value stream.

We'll cover the following topics:

• Death to Silos: developing an culture of collaborative software delivery
• Developing communication and bridge-building skills
• Understanding your business and its domain
• The automated "infrastructure as code" revolution
• Driving performance, process, and people improvements through metrics
• The DevOps' Toolkit: Puppet, Chef, Flapjack, Vagrant, and friends

Portable Cloud Storage with jclouds

Adrian Cole

Thursday 1:30 PM - Himarshee

Key/value stores are the most common storage offerings in the cloud today. While conceptually similar, BlobStores present different programming models and consistency models that must be considered in application design. After this session, you'll understand these differences, and know how to use jclouds to avoid cloud lock-in and increase testability without restricting access to cloud-specific features.

We'll start by comparing public cloud services like Amazon S3 or Microsoft Azure and private cloud software like OpenStack Swift or Eucalyptus Walrus from a feature and code/API level. We'll then review java and clojure calls to the open source jclouds BlobStore API, abstracting away these differences. We'll finish with a review of integration patterns in production today you can consider while designing your cloud architecture.

Vagrant: Virtualized Development Environments Made Simple

Matt Stine

Thursday 1:30 PM - Atlantic VI

Have you ever wished that your local development sandbox could look exactly like production, but you've got a mismatch between your local OS and your production OS? And what about the age old "it works on my machine" excuse that quite often stems from differences between developer sandboxes? Many have turned to virtualization, creating a machine image that can be passed around the team. But who manages the template? How do you keep things in sync?

In this session, we'll explore Vagrant (http://www.vagrantup.com), an open source tool that allows you to easily create and manage virtual development environments that can be provisioned on demand and "thrown away" when no longer needed.

Our agenda will include:

• Creating new base OS templates using the Vagrant Veewee plugin
• Creating a new development box using Vagrant
• Provisioning the box using Puppet
• Provisioning the box using Chef
• Deploying a simple web application to a multi-box development environment
• Packaging and distributing the box within your team

Plugging Into Gradle Plugins

Tim Berglund

Thursday 7:30 PM - Atlantic V

Gradle is being adopted by enterprises and open-source projects alike for its ease of use, flexibility, and compatibility with existing standards. However, Gradle's true strength shines not when it is viewed as a wrapper around standards, but as a toolkit for creating your own standards to reflect your build patterns and practices. It is extensible at every level, but most powerfully at the level of Gradle plugins.

In this session, you'll learn the Gradle APIs you need to know to develop a plugin, the different ways to organize and distribute plugins, and the way you should use plugins as a means of extending the Gradle DSL to describe your build domain in a concise and idiomatic way. Examples will use real code for a plugin written by Tim and Matthew that can be used in development and automated deployment settings.

DIY NoSQL: Spinning up services with Whirr

Adrian Cole

Thursday 7:30 PM - Himarshee

Whether it's HBase, Cassandra or one of the many others, you've probably already heard about NoSQL. Perhaps you have a continuous test flow dependency, yet are concerned about learning curve or infrastructure required for the NoSQL store you need.

During this talk, you'll see how you can transform infrastructure clouds such as Amazon EC2 or GoGrid into your data cluster using Apache Whirr.

We'll start by reviewing cloud provisioning and how Whirr adds service management to the underlying jclouds ComputeService API. You'll then learn whirr syntax and how to use it from the commandline or via a Java API. Finally, we'll discuss patterns for workflow integration. When you leave, you'll know how to setup and use NoSQL stores with a lot less work.

Glu-ing the last Mile

Ken Sipe

Friday 9:00 AM - Himarshee

How does your team handle release weekend? Is it the whole weekend? Is everyone on call? Is there a way to reverse the decision mid-stream?... How long would it take your company or team to push a single line code fix from dev into production? Way too many organizations handle the production release through manual and tedious labor following a lengthy to-do check list. Way too many organizations have no way to reproduce their production environment... because they have manually changed or updated configurations without version control... or they have OS or application server paths that are not under proper management.

What if you could "test" your production release before production? One of the answers to the last mile of continuous delivery is GLU. GLU is an open source project for deployment automation. It was created by one of the co-founders of LinkedIn (Yan Pujante) for automation of LinkedIn's deployment automation.

This session is a basic tutorial, walking through the configuration of a deployment out to multiple services. We will work through serial and parallel deployments, ensuring consistency and detecting problems. This session should be a sufficient introduction to walking through: 1) installation, 2) configuration, 3) multi-server deployments 4) manual updates and 5) automated updates

Continuous Delivery All-day Workshop, Pt. 1: Deployment Pipelines

Neal Ford

Friday 9:00 AM - Atlantic V

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In this workshop we take the unique approach of moving from release back through testing to development practices, analyzing at each stage how to improve collaboration and increase feedback so as to make the delivery process as fast and efficient as possible. At the heart of the workshop is a pattern called the deployment pipeline, which involves the creation of a living system that models your organization's value stream for delivering software. We spend the first half of the workshop introducing this pattern, and discussing how to incrementally automate the build, test and deployment process, culminating in continuous deployment.

Jenkins Continuous Integration Half-day Workshop

Matthew McCullough

Friday 9:00 AM - Atlantic VI

The team dynamics and agile process revolution of the last several years has taught us that continuous integration (CI) is a necessary part of a healthy agile team. Jenkins (formerly Hudson) is the idea and footprint leader in the CI space. A recent survey stated that over 70% of all CI installations have Jenkins in their DNA. What's so awesome about this particular CI tool?

Get on board with a ground-up survey of how to install, apply, upgrade, and leverage the free an open source Jenkins Continuous Integration server for your build, whether it be Ant, Maven, Gradle, JavaScript, Rake, or just shell scripts.

In this workshop, you'll learn how to add plugins for additional build and analysis phases, how to cluster Jenkins on a subnet for a swarm of CI servers that automatically load balance and collate reports, and lastly, how to manage Jenkins on a disparate set of OSes to natively test your unit and integration tests on all your supporter platforms.

Jenkins Continuous Integration Half-day Workshop

Matthew McCullough

Friday 10:45 AM - Atlantic VI

The team dynamics and agile process revolution of the last several years has taught us that continuous integration (CI) is a necessary part of a healthy agile team. Jenkins (formerly Hudson) is the idea and footprint leader in the CI space. A recent survey stated that over 70% of all CI installations have Jenkins in their DNA. What's so awesome about this particular CI tool?

Get on board with a ground-up survey of how to install, apply, upgrade, and leverage the free an open source Jenkins Continuous Integration server for your build, whether it be Ant, Maven, Gradle, JavaScript, Rake, or just shell scripts.

In this workshop, you'll learn how to add plugins for additional build and analysis phases, how to cluster Jenkins on a subnet for a swarm of CI servers that automatically load balance and collate reports, and lastly, how to manage Jenkins on a disparate set of OSes to natively test your unit and integration tests on all your supporter platforms.

Continuous Delivery All-day Workshop, Pt. 1: Deployment Pipelines

Neal Ford

Friday 10:45 AM - Atlantic V

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In this workshop we take the unique approach of moving from release back through testing to development practices, analyzing at each stage how to improve collaboration and increase feedback so as to make the delivery process as fast and efficient as possible. At the heart of the workshop is a pattern called the deployment pipeline, which involves the creation of a living system that models your organization's value stream for delivering software. We spend the first half of the workshop introducing this pattern, and discussing how to incrementally automate the build, test and deployment process, culminating in continuous deployment.

Glu

Ken Sipe

Friday 10:45 AM - Himarshee

One aspect of getting your continuous delivery pipeline right is the deployment pipeline. For "continuous" delivery you will need to have a way to automate the instantiation of the entire technology stack, as well as a quick and easy detection of what changed on a server. Glu is a open source tool for providing this capability through a the modeling of the deployment platform.

This workshop will go beyond a walk through of Glu's capabilities providing a hands-on tutorial style labs.

Running in the Cloud with Chef

Jeffrey Hulten

Friday 1:30 PM - Atlantic VI

The dynamic nature of services like Amazon's EC2 let us build our applications with the intent to scale horizontally if your business succeeds. Unfortunately the traditional way of managing servers just doesn't cut it when you need to add two more application servers in the next 20 minutes.

Chef is one of the rising stars of the "Infrastructure as Code" tools. In this session we will start with a blank Chef repository and build our configurations to deploy a WAR on multiple Tomcat instances behind Apache.

Continuous Delivery All-day Workshop Pt 2: Agile Infrastructure

Neal Ford

Friday 1:30 PM - Atlantic V

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In the second half of the workshop, we introduce agile infrastructure, including the use of Puppet to automate the management of testing and production environments. We'll discuss automating data management, including migrations. Development practices that enable incremental development and delivery will be covered at length, including a discussion of why branching is inimical to continuous delivery, and how practices such as branch by abstraction and componentization provide superior alternatives that enable large and distributed teams to deliver incrementally.

Glu

Ken Sipe

Friday 1:30 PM - Himarshee

One aspect of getting your continuous delivery pipeline right is the deployment pipeline. For "continuous" delivery you will need to have a way to automate the instantiation of the entire technology stack, as well as a quick and easy detection of what changed on a server. Glu is a open source tool for providing this capability through a the modeling of the deployment platform.

This workshop will go beyond a walk through of Glu's capabilities providing a hands-on tutorial style labs.

Mockito Workshop

Szczepan Faber

Friday 3:15 PM - Himarshee

Do you want to learn more about Mockito framework directly from the founder? Join the workshop and get up to speed with:

• principles of interaction testing
• using test spies to drive the design and high quality production code
• getting most of the test spy pattern to produce readable and maintainable tests
• solutions to typical unit testing challenges with regards to mocking
• Mockito features and patterns along with the use cases when they are most useful
  

See you at the workshop! Please take your laptop so that you can code the exercises in your own, most friendly environment.

Continuous Delivery All-day Workshop Pt 2: Agile Infrastructure

Neal Ford

Friday 3:15 PM - Atlantic V

Getting software released to users is often a painful, risky, and time-consuming process. This workshop sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours?sometimes even minutes?no matter what the size of a project or the complexity of its code base.

In the second half of the workshop, we introduce agile infrastructure, including the use of Puppet to automate the management of testing and production environments. We'll discuss automating data management, including migrations. Development practices that enable incremental development and delivery will be covered at length, including a discussion of why branching is inimical to continuous delivery, and how practices such as branch by abstraction and componentization provide superior alternatives that enable large and distributed teams to deliver incrementally.

Cooking Lessons: Hands on with Chef

Jeffrey Hulten

Friday 3:15 PM - Atlantic VI

After seeing the possibilities of "Infrastructure as Code" with Chef you will have a chance to try it out. In this workshop we will start with a blank Chef repository and build our configurations to deploy a WAR on multiple Tomcat instances behind Apache.

For this workshop you will need a laptop and Oracle VirtualBox 4. Make sure you download the software before the session begins. A virtual machine will be distributed with the pieces you need to participate.