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.

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.

Today’s open-source offerings allow teams to quickly and easily setup their own infrastructure for things like source management and builds. In this overview session, we'll survey some of these offering and see how to make them work to our advantage towards a Continuous Delivery model.

Participants should bring either a Windows or Mac laptop for working through the examples.

Notes:

We're looking forward to having you in the DIY Infrastructure workshop. To maximize the learning and value of our time together, we ask that you prepare your notebook that you're bringing to this hands on workshop.

1) Choose a Windows or Mac laptop that you'll be bringing to the workshop (we have some downloads and installs that are better to do before the event). Ensure you have admin or sudo privileges on the machine. Since we will be running a virtual machine on this system throughout the workshop, if you have a choice of laptops, please bring the one with a higher amount of memory and processor power.

2) Install VirtualBox on your system prior to the workshop. To simplify using all of the software that we'll be running in this session, we'll be making use of VirtualBox. You can install VirtualBox from www.virtualbox.org. (Note - the site currently seems to have an expired certificate which produces dire warnings in some browsers.) Take note of the directory where you install it. We'll need this information in the session.

3) Verify that you can start up ViritualBox and that it comes up successfully on your laptop. No more configuration is necessary.

In this 3/4 day workshop, we’ll learn how to utilize common free, open-source applications such as Cucumber, Aruba, Puppet, GIT, Jenkins, Sonar, Geb, and Spock to create a simple pipeline for managing and delivering a sample product. We will also discuss the principles of Continuous Delivery and model them as we setup our simple pipeline to do automatic builds, testing, and deployment of a sample web project - all running in a virtual machine on your laptop. We'll also talk about tooling to help automate database version management and look at scripting that can automatically extract and notify you of things like code quality metrics. Finally, we'll look at how to use some of the newest testing tools to make your testing easier.

Many Git classes successfully focus on the basics for those new to DVCS. However, with Git having 7 years on the street now, there is a growing desire to address the maturing users of this innovative DVCS. This class will take existing Git users and bring them to a heightened level of productivity by leveraging Git's powerful, yet under-used advanced features.

Git has established itself as an important new version control system and many progressive developers have already moved to this exciting system. After a few months of using the basics, passionate developers may begin to wonder what advanced features Git has to offer. These advanced Git usages are scarcely documented, and for the first time in a live class, they are demonstrated in an easy-to-grasp form with the use case, operation, and behavior all thoroughly explained.

Gradle. Another build tool? Come on! But before you say that, take a look at the one you are already using.

Whether your current tool is Make, Rake, Ant, or Maven, Gradle has a lot to offer. It leverages a strong object model like Maven, but a mutable, not predetermined one. Gradle relies on a directed acyclic graph (DAG) lifecycle like Maven, but one that can be customized. Gradle offers imperative build scripting when you need it (like Ant), but declarative build approaches by default (like Maven). In short, Gradle believes that conventions are great -- as long as they are headed in the same direction you need to go. When you need to customize something in your build, your build tool should facilitate that with a smile, not a slap in the face. And customizations should be in a low-ceremony language like Groovy. Is all this too much to ask?

Gradle has received the attention of major open source efforts and has chalked up significant conversions by the Spring Integration, Hibernate, and Grails projects. What do these technology leaders see in this bold new build tool? They see not only a better way to build Java applications, but an extensive ecosystem of connecting to existing Ant and Maven build files while expanding the horizon of test, CI, and deployment automation in an easy manner. Join us for 90 minutes and let us take you on this same walk of discovery of the most innovative build tool you've ever seen.

Join me for this 3/4 day Jenkins introduction workshop. We'll learn Jenkins from the ground up and work through examples to ensure you feel comfortable with using it and understanding it before the workshop ends.

Participants should bring either a Windows or Mac laptop to work through the workshop exercises.

Topics covered:

· What Jenkins is

· The Jenkins “object model”

· Global Configuration (first steps)

· Setting up build jobs and navigating around Jenkins

· Customizing Jenkins – adding parameters and utilizing environment variables

· Jenkins Plugins

· Building an example project with Jenkins and Git

· Setting up polling for changes

· Using the Jenkins command line interface

     Scripting Jenkins with Groovy

Notes:

We're looking forward to having you in the Jenkins workshop. To maximize the learning and value of our time together, we ask that you prepare your notebook that you're bringing to this very hands on workshop.

1) Choose a Windows or Mac laptop that you'll be bringing to the workshop (we have some downloads and installs that are better to do before the event). Ensure you have admin or sudo privileges on the machine.

2) Please have a recent Java JDK installed.

3) Download and install the latest Jenkins to your machine from: http://mirrors.jenkins-ci.org

4) Please have Git installed prior to attending the workshop. There's no need to "configure it" beyond the basic install. Installation instructions can be via operating-system specific pages at: http://help.github.com/win-git-installation/ http://help.github.com/mac-git-installation/

5a) Test your git setup is working by running git --version at your terminal prompt on Mac or at your "Git Bash Prompt" on Windows. Verify the output says Git is version 1.7 or higher.