Standard Build and Deploy
|Photo credit: nyuhuhuu on Flickr|
This was where the drive for the standard build came from, to have something which would be the "de-facto" process, where the components would be built and packaged, and if it didn't build there, it was regarded as a failure.
With time, the IDEs were standardised, but I do remember impressing on my team on more than one occasion that "It doesn't matter if it builds in JBuilder. It doesn't matter if it builds in Netbeans. All that matters is that it builds when I build it using the standard build ant task".
Using a tool like ant, it's only a small step to run tasks to carry out deployments, and having spent some time going back to manual deployments (in a case where there were no tasks implemented) the value of these were underlined even more.
Summary of Gains
- Consistency of builds
- Easier management of build artefacts (built code libraries and also support files)
- Faster deployment of artefacts for testing