Agile Automation
Who Should Attend/Prerequisites
Developers whare interested in increasing the level of automation in their projects.
Class Size Limit: 16 (Minimum 0)
Course Overview
The speed at which Agile projects run demands a high level of automation surrounding any repetitive activities. Nwhere is this more obvious than in a build/test/deploy process. Builds have traditionally been a source of pain and the natural reaction tthis pain is for teams tput off the build and deployment activities thereby incurring large amounts of 'project debt'. In an Agile world we attack this problem by accelerating and automating the build and deployment processes. The goal of this class is teducate a team on how tapply automation tall stages of their work.
We incrementally build a complete Continuous Integration strategy that is applicable and configurable for most any environment.
Agenda
- One step builds
- Scheduled builds
- Push button releases
- Installation and deployment
- And monitoring for all...
- Directory structure exercise on use of SubVersion in Eclips
- Building from the command line
- Scripting the build
- Ant exercise on putting together build scripts
- Why
- How
- Cron exercise
- CruiseControl exercise on install, exercise on use, exercise on project setup, exercise on cctray
- What
- eMail notifications exercise on CruiseControl notification configuration
- Website status
- What is a release?
- How should this affect the code tree?
- Packaging the release, and the relationship testing
- Creating a distribution
- Tagging the release
- Automating all of the above exercise on use of and produce daily releases
- What goes wrong in an installation and how we deal with that
- Diagnostic testing during installation exercise in writing installation diagnostic tests
- Installers and how they help exercise in use of IzPack for Fedora targets
- Issues specific tJ2EE hosted applications and how hot deployment is used
- Autupdating: you know what it is, now how can we dit in this environment?
- JWS and autupdating. Is this the total solution?
- More CruiseControl publishers exercise in SMS and RSS for CruiseControl
- The cool stuff: visual information reflectors
- Monitoring your installed base with log4j and Trip Wires
- Automating a crash report
Cost:
$1,200 per attendee.