| View: | [ 2009 | 2008 | 2007 | 2006 | 2005 | 2004 | 2003 ] |
| Articles Links | Projects |
- Automation for the people: Hands-free database migration by Paul Duvall - [Clicks: 3]
Databases are often out of sync with the applications they support, and getting the database and data into a known state is a significant challenge to manage. In this installment of Automation for the people, automation expert Paul Duvall demonstrates how the open source LiquiBase database-migration tool can reduce the pain of managing the constant of change with databases and applications.
http://www.ibm.com/developerworks/java/library/j-ap08058/index.html - Aug, 2008 - Automation for the people: Continual refactoring by Paul Duvall - [Clicks: 6]
Refactoring is a well-accepted practice for improving existing code. Yet, how do you find the code that should be refactored, in a consistent and repeatable manner? This installment of Automation for the people explains how to use static analysis tools to identify code smells to refactor, with examples showing how to improve odiferous code.
http://www.ibm.com/developerworks/java/library/j-ap07088/index.html - Jul, 2008 - Automation for the people: Pushbutton documentation by Paul Duvall - [Clicks: 2]
Project documentation is often one of the necessary evils in delivering a software product. But imagine being able to generate your documentation at the click of a button. In this installment of Automation for the people , automation expert Paul Duvall explains how you can use open source tools to automate the generation of Unified Modeling Language (UML) diagrams, build figures, entity-relationship diagrams (ERDs), and even user documentation.
http://www.ibm.com/developerworks/java/library/j-ap06108/index.html - Jun, 2008 - Automation for the people: Manage dependencies with Ivy by Paul Duvall - [Clicks: 10]
Managing source-code dependencies among projects and tools is often a burden, but it doesn't need to be. In this installment of Automation for the people, automation expert Paul Duvall describes how you can use the Apache Ant project's Ivy dependency manager to handle the myriad dependencies that every nontrivial Java project must manage.
http://www.ibm.com/developerworks/java/library/j-ap05068/index.html - May, 2008 - Automation for the people: Continuous Integration anti-patterns, Part 2 by Paul Duvall - [Clicks: 11]
While Continuous Integration (CI) can be extremely effective at reducing risks on a project, it requires a greater emphasis on your day-to-day coding activities. In this second installment of a two-part article on CI anti-patterns, automation expert and co-author of Continuous Integration: Improving Software Quality and Reducing Risk, Paul Duvall, continues laying out CI anti-patterns, and more importantly, demonstrates how to avoid them.
http://www.ibm.com/developerworks/java/library/j-ap03048/index.html - Mar, 2008 - Automation for the people: Speed deployment with automation by Paul Duvall - [Clicks: 10]
Automated builds aren't just for development teams - they can be extended to facilitate moving software from development all the way into production. In this installment of Automation for the people, automation expert Paul Duvall describes how to use Ant with Java Secure Channel for remotely deploying software into multiple target environments.
http://www.ibm.com/developerworks/java/library/j-ap01088/index.html - Jan, 2008
- Continuous Integration Server Feature Matrix - [Clicks: 22]
There are many Continuous Integration systems available. This page is an attempt to keep an unbiased comparison of as many as possible of them. The goals are: * Make it easier to choose an appropriate CI tool for your project; * "Healthy competition aid" for the people involved in the development of these various CI systems.
http://damagecontrol.codehaus.org/Continuous+Integration+Server+Feature+Matrix
- Hudson: a continuous build system - [Clicks: 15]
Hudson monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Hudson focuses on the following two jobs: 1) Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Hudson provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continoues build increases the productivity. 2) Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them dilligently and notice when it broke. Hudson keeps those outputs and makes it easy for you to notice when something is wrong.
https://hudson.dev.java.net/