Grails hudson ixxus_template
0 likes307 views
This document discusses continuous integration using Hudson. It defines continuous integration and explains why it is needed to avoid integration problems and allow teams to develop software more rapidly. Hudson is recommended for continuous integration because it is open source, easy to use, supports various source control management and build tools, and can integrate with LDAP and be scaled out. The process overview shows how Hudson will poll for code changes, check out and test the code, build artifacts, deploy them, and tag the build.
Grails hudson ixxus_template
- 1. Grails & HudsonLean Java EngineeringRobin BramleyOctober 20101
- 2. About meA hands-on Senior Architect at IxxusWorking on Grails & Alfresco projectsWorked for consultancies for the last 12 yearsLead Architect on Virgin Money Giving – a finalist in the BCS 2010 AwardsTechnical Architect on several phases of the award winning ConCert programme at AonContributions to a wide range of Open Source projects including adding OpenID support to Spring Security14 years Java, 5 years Spring/Hibernate, 4 years Groovy, 3 years Grails, 2 years Hudson...
- 3. 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
- 4. Why is CI needed?It works on my machineOops, 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
- 5. Andon lights
- 7. Ownership of issueReproduced with permission
- 10. Easy to use:
- 11. Distributed as a Java war-file
- 12. SCM support
- 15. Notifications
- 16. Easy to extend with plug-ins
- 17. Collates trend statisticsWhy Hudson (for the Enterprise)?Can integrate with LDAP for authentication/authorisation
- 18. Supports master/worker for scale-out
- 19. IDE plug-ins available (e.g. )
- 20. Remote accessAPI
- 21. Commercial support option fromWhat will we see?SCM integrationPolling for changesCheck outTaggingTestingUnit / integration testsFunctional testsAnalysisCodeNarcCoberturaAutomated deployment
- 22. Process overview1. Test locally (automated & manual)2. Check in3. Hudson polls the code repo4. Hudson triggers job5. Hudson checks out code6. Hudson compiles & tests code7. Hudson builds war8. Hudson deploys war9. Hudson tags the build
- 23. Demo
- 24. Questions?Robin BramleyBlog: http://leanjavaengineering.wordpress.comTwitter: @rbramleyLinkedIn: http://uk.linkedin.com/in/rbramley