• Save
Grails hudson ixxus_template
Upcoming SlideShare
Loading in...5
×
 

Grails hudson ixxus_template

on

  • 776 views

 

Statistics

Views

Total Views
776
Views on SlideShare
651
Embed Views
125

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 125

http://skillsmatter.com 90
http://smash 35

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Grails hudson ixxus_template Grails hudson ixxus_template Presentation Transcript

    • Grails & Hudson
      Lean Java Engineering
      Robin Bramley
      October 2010
      1
    • About me
      A hands-on Senior Architect at Ixxus
      Working on Grails & Alfresco projects
      Worked for consultancies for the last 12 years
      Lead Architect on Virgin Money Giving – a finalist in the BCS 2010 Awards
      Technical Architect on several phases of the award winning ConCert programme at Aon
      Contributions to a wide range of Open Source projects including adding OpenID support to Spring Security
      14 years Java, 5 years Spring/Hibernate, 4 years Groovy, 3 years Grails, 2 years Hudson...
    • Continuous Integration
      “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
    • Why is CI needed?
      It works on my machine
      Oops, I forgot to run tests before that check in...
      I’ll just check my work in before I go home...
      It helps to encourage better developer behaviour
    • Andon lights
    • Extreme feedback
    • Ownership of issue
      Reproduced with permission
    • Why Hudson?
      • Open Source
      • Award winning
      • Easy to use:
      • Distributed as a Java war-file
      • SCM support
      • Build tool support
      • Post build actions
      • Notifications
      • Easy to extend with plug-ins
      • Collates trend statistics
    • Why Hudson (for the Enterprise)?
      • Can integrate with LDAP for authentication/authorisation
      • Supports master/worker for scale-out
      • IDE plug-ins available (e.g. )
      • Remote accessAPI
      • Commercial support option from
    • What will we see?
      SCM integration
      Polling for changes
      Check out
      Tagging
      Testing
      Unit / integration tests
      Functional tests
      Analysis
      CodeNarc
      Cobertura
      Automated deployment
    • Process overview
      1. Test locally (automated & manual)
      2. Check in
      3. Hudson polls the code repo
      4. Hudson triggers job
      5. Hudson checks out code
      6. Hudson compiles & tests code
      7. Hudson builds war
      8. Hudson deploys war
      9. Hudson tags the build
    • Demo
    • Questions?
      Robin Bramley
      Blog: http://leanjavaengineering.wordpress.com
      Twitter: @rbramley
      LinkedIn: http://uk.linkedin.com/in/rbramley