Monday, April 17, 2017
Thursday, June 18, 2015
- A new and more responsive user interface
- Great improvement on UI performance for larger archives (10x-15x faster)
- Command line deployment configuration is independent from artifact packages
- Command line deployment xml configuration can be managed outside kwatee
- ... and many other improvements
Wednesday, December 3, 2014
- An new experimental User Interface that improves usability but also responsiveness and performance.
- An extensive JSON Rest API with Python and Java client libraries
- An improved deployment mechanism
- Stability improvements
Tuesday, July 15, 2014
Wednesday, April 18, 2012
Wednesday, February 22, 2012
Kwatee Agile Deployment 2.1 has just been released. The major news of version 2.1 is that Kwatee is now free to use for personal and commercial purposes without any functionality or time restriction.
There are great improvements in the creation and definition of variables. A notable enhancement is the introduction of the Version Variable panel which shows all the variables that are used either in archive files or actions and makes it possible to define default values which can be overriden in deployments.
Thursday, January 19, 2012
|Image: dream designs / FreeDigitalPhotos.net|
A financial software that processes millions of transactions per hour or a mobile network monitoring system that tracks the quality of every single call for an entire country in real-time, now these are example of complex systems which raise serious challenges.
Updating software involve copying files, setting up application and system security parameters, upgrading database schema and possibly configuring startup/cron configurations; that's about it.
So where is this so called complexity? And why is it that, more often than not, it takes less time to develop, test and package a new software update than to upgrade a customer deployment?
Ok, I admit that I'm leaving out some details but the truth is that while it doesn't take a rocket scientist to do software deployment, there are difficulties of a different kind:
- It's a mind-bogglingly dull task: repetitiveness is an attention killer and increased release frequency resulting from agile development processes doesn't help.
- Some applications must be updated on tens of servers. This type of repetition has even worse consequences on the mental sanity of the deployers.
- Previous application configuration parameters must be re-applied to the new update. Since these are not always strictly documented, the safer procedure usually involves a careful and time-consuming inspection of the differences between old and new versions of all the files to copy changes over.
- Implicit knowledge: the documentation of installation procedures is often slim and riddled with unwritten assumptions, relying on the experience gathered by deployment engineers over time.
So don't go looking for rocket scientists. All you need is a bunch of mindless and unerring drudges or ... empower your IT team with good agile deployment software to make their work immensely more efficient and rewarding but that will be another story.
Monday, January 16, 2012
Besides a major revamp of the user interface for better usability and readability, Kwatee 2.0 introduces telnet/ftp support for windows deployment, Amazon EC2 and ELB cloud deployment, AIX deployment support, and many more features. See the revision history for full details.
Tuesday, July 5, 2011
|Image: Danilo Rizzuti / FreeDigitalPhotos.net|
Continuous integration has become the bread and butter of most development teams to insure that code changes from a team of developers are automatically built and tested to detect integration errors as early as possible.
Continuous delivery goes one step beyond that by extending the chain and making automated builds available for production. A pre-requisite for continuous delivery is system integration testing. Automating system integration testing is more difficult than unit testing, particularly for applications with many moving parts deployed on more than one servers.
A key-step in implementing Continuous Delivery is to extend your CI process with an automated software configuration and deployment management system.
Saturday, June 18, 2011
|Image: Suat Eman / FreeDigitalPhotos.net|
We need a mechanism that keeps track of every deployed file changes (as they really are on the target server) so that only modified files get updated.
Friday, June 17, 2011
|Image: photostock / FreeDigitalPhotos.net|
That rather straightforward requirement is actually pretty difficult to satisfy because of the variety of operating systems on which the application may be running, the fact that there may be several versions of the application to support, etc.
One step in the right direction is to use virtual machines.
Tuesday, June 14, 2011
|Image: worradmu / FreeDigitalPhotos.net|
Thursday, May 12, 2011
There are several options available, both commercial and open source. Here's a short list of free ssh servers that can easily be installed on your Windows servers:
Monday, May 9, 2011
Monday, April 25, 2011
In this post we provide a simple Python library that makes this automation event simpler as well as some very simple examples.
Wednesday, April 13, 2011
kwateeSDCM provides a central repository for software and configuration, auditing of configuration changes, multiple configuration sets (i.e. test, production, ...), single click rollout and software & configuration versioning through a user friendly web interface. The full-featured Community Edition provides major enterprise-grade benefits such as:
- Major reduction of software upgrade rollout time
- Quick rollback to previous software version or configuration
- Reliable and repeatable deployment operational procedures
- Guaranteed integrity of installed software & configuration
Check out the tutorials and download the package to see for yourself