Skip to main content

Continuous Integration 101 at Agile Cambridge

Image
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

I, Robot

By
The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...
1 comment
Read more

It's great to be back at the ACCU Conference 2025!

By
Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...
1 comment
Read more

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