Java deployments are often messy, error-prone, and manual, leading to delays in making software available to users. In Part 1 of a two-part article in the Automation for the people series, automation expert Paul Duvall identifies a collection of key patterns for developing a reliable, repeatable, and consistent deployment process capable of generating one-click deployments for Java applications.
Here is the story of how in a single morning we migrated our repositories (not a large number of codebases) from Subversion to Git. I won't include much configuration commands, since there are already very good howtos that I now know by heart and which you can follow to setup your own Git server. What I'll tell you in this article are our experience in migrating and the whole story of how we did it from scratch (an additional, empty virtual server).
This article explains why Agile development teams must deliver and keep delivering on a regular schedule. The surest proof of your team's practicing Agile methodology correctly is that you continue delivering working product.
Often, an existing database application must evolve rapidly by incremental steps. Alex describes a tried and tested system to provide an automated approach to deploying both new and existing database systems, whilst dealing with common security and configuration issues.
The cost impact to a company of a failed project can be severe indeed. The impact on the reputation of the project manager can be disastrous. Numerous methodologies are available for mitigating these risks – PRINCE2, RUP, DSDN, eXtreme programming – and these have helped to some extent. This document introduces the 3D™ methodology – a set of best practices and quality tools developed by BuildMonkey, which can be summarised as: De-risk. Deploy. Deliver.
The increasing popularity of agile development methods is putting new demands on the traditional CM discipline. A working CM environment is essential for the rapid nature of agile development methods, but the CM process and the CM role has to be adapted to the present evolution of software development methods as well as automated tools. This article discusses lean principles and agile values within a CM scope and also introduces a method to classify the CM discipline in relation to development method and level of tool automation.
Agile development is the future of modern software engineering. Companies that have implemented it successfully have seen great improvements in their software—both in cost, stability, and in the utility of the software itself. However, some companies have struggled, finding it difficult to adapt their processes and culture to work in an Agile environment. One of the areas that best highlights the cultural shifts required to become an Agile organization is Continuous Integration (CI).
Combine tried-and-true old friend Apache Ant with the trendy Twitter service to create a build-notification system that doesn't rely on Ant's mail task. By receiving status updates via Twitter after an automated Ant build completes, project developers and testers are notified immediately that the new build is available. And they can subscribe and unsubscribe to the feed at will.
This article covers Flash compilation and linkages, dependency scope, RSL support, WAR packaging, build profiles and the ASDoc goal. By the end of this article you should have all the tools you need to manage your enterprise project with Maven and Flexmojos.
In the course of rescuing a development from 'merge misery', it became increasingly apparent that there were a number of practices for managing branches in the Version Control System that would have reduced the pain and effort of the subsequent merge, and made the dream of continuous delivery come closer to reality. From the experience comes some well-tested ways of making branches and merges a stress-free part of application development.