Skip to main content

Continuous Integration 101 at Agile Cambridge

By
What: Continuous Integration 101

Where: Agile Cambridge, Cambridge, UK

When: Thursday 26th September 2013, 2pm to 3.30pm

I will be giving a stripped down version Naked Element's Continuous Integration 101 course at this years Agile Cambridge.

Continuous Integration 101

“Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.”

-- Martin Fowler 

Course Objectives

Continuous Integration 101 is a foundation continuous integration course for Java developers. It is a practical course that can be completed within a working day in most cases. After completing the course you will:

  • Understand what continuous integration is and why it is so important 
  • Be able to create Java projects and build them with Ant and/or Maven so that they can be run by Jenkins. 
  • Be able to create continuous integration jobs with Jenkins 

And if time allows:

  • Be able to notify developers of changes to the build status 
  • Be able to monitor code quality with Sonar 

Who should take Continuous Integration 101?

Anyone with a working knowledge of Java who would like to learn about continuous integration. This includes developers, testers, build engineers and anyone else who needs to create and/or maintain Java based continuous integration.

Prerequisites

To get the most out of this course you'll require basic knowledge of:

  • Java
  • A Java IDE (such as Eclipse)
  • Source Control Management

To complete the exercises in this course you will need the following software installed before attending the session. There will not be time to install it in the session. Assume latest versions unless otherwise stated:

  • Java IDE (e.g. Eclipse)
  • Java SDK (1.7+)
  • Version Control System (e.g. Subversion 1.7 (1.8 does not work with the current version of Jenkins) and SubClipse for Eclipse integration)
  • JUnit (JARs only)
  • Jenkins (Configured for SMTP, JDK and Maven)
  • Version Control System (e.g. Subversion) plugin
  • Sonar plugin (configured)

If time allows, the further exercises require the following:

  • Jacoco (JARS only)
  • Sonar (default install locally)

Full instructions on how to install all of the prerequisites on Windows, Mac and Linux are included a downloadable lab sheet here. Please come prepared.

Comments

Post a Comment

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

By
I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...
Post a Comment
Read more

Catalina-Ant for Tomcat 7

By
I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...
22 comments
Read more

RESTful Behaviour Guide

By
I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...
1 comment
Read more