Automated deployment with Maven and friends
I’m busy with an automated deployment configuration task and stumbled upon the following excellent presentation by John Ferguson Smart from Wakaleo Consulting: Automated deployment with Maven and friends – Going the whole nine yards
If I can add some context to labelling the presentation as excellent. In essence it represents what I regard as best practices. Setting up the mentioned infrastructure takes time, but WILL save time and money in the long run. Here are some other reasons why I advocate the use of the practices outlined in the presentation:
- I’ve had the misfortune of a three month stint as a human continuous integration / deployment “Jenkins” in the early days of a large scale enterprise project, this has left me scarred and obsessed with automated deployment and subsequent testing.
- I’ve seen Liquibase replicated many times, at considerable expense.
- If you don’t set it all up early in a project, you will pay for it with wasted time, one way or the other.
Note to self – don’t be that anonymous “someone that forgot to add 29 February” to the system
Overheard someone talking about some systems being down whilst shopping at the mall today. Well I had largely forgotten that its a leap year, nor given the date much thought.
There where no doubt thousands of systems that had glitches associated with 29 February today, and covering it up is most likely standard procedure, and who could blame the companies in question.
In any case, one of the biggest crashes of the day, that made the news, seems to be a health care payment system processing 150 000 transactions per day, the best line is this, and I hope SVN will never show this I’m this someone:
A knowledgeable source said the outage arose because “someone forgot to add the 29th of February” to the system.
Well, it seems its called the Leap year bug, and here are some more occurances:
