| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

Hudson

Page history last edited by Manuel Kueblboeck 13 years, 3 months ago

Hudson has been chosen as CI tool for the following reasons:

  • Automatically build the Java code and run JUnit tests on every submit to Subversion.
  • Easy installation: Just java -jar hudson.war, or deploy it in a servlet container. No additional install, no database.
  • Easy configuration: Hudson can be configured entirely from its friendly web GUI with extensive on-the-fly error checks and inline help. There's no need to tweak XML manually anymore.
  • Change set support: Hudson can generate a list of changes made into the build from CVS/Subversion. This is also done in a fairly efficient fashion, to reduce the load of the repository.
  • RSS/E-mail/IM Integration: Monitor build results by RSS or e-mail to get real-time notifications on failures.
  • After-the-fact tagging: Builds can be tagged long after builds are completed
  • JUnit/TestNG test reporting: JUnit test reports can be tabulated, summarized, and displayed with history information, such as when it started breaking, etc. History trend is plotted into a graph.
  • Distributed builds: Hudson can distribute build/test loads to multiple computers. This lets you get the most out of those idle workstations sitting beneath developers' desks.

 

Useful plugins:

 

 

Deployment pipeline

  • Check Post-build Action: Build other projects and Aggregate downstream test results on previous stage

 

blog post about web application testing with Hudson and Selenium

See also: Continuous Deployment

Comments (0)

You don't have permission to comment on this page.