Kwatee Changelog

New in version 2.3.2

December 11th, 2014
  • Bug fix: java api package upload
  • Bug fix: error when creating server on postgresql DB
  • Bug fix: server test connection bug when using private keys

New in version 2.3.1 (December 5th, 2014)

  • Bug Fixes:
  • Distinguish between empty variable and undefined variable
  • Allow . (dot) in variable names
  • Re-introduced "Reedit" function in experimental interface
  • Fixed kwatee-maven-plugin pom.xml in addOns
  • Added kwatee-api-java pom.xml in addOns

New in version 2.3.0 (December 4th, 2014)

  • New: experimental user interface
  • New: JSON RESTful API
  • New: python api
  • New: java api
  • Enhancement: Re-introduced "Duplicate Environment" feature (only SNAPSHOT deployment is copied).
  • Enhancement: kwateee metadata files are no longer installed together with installed artifact; instead they are centrally located in kwatee_root_dir.
  • Enhancement: action can return exit codes to indicate success/failure instead of special kwatee markers.
  • Enhancement: kwatee variables can be declared in package files with a default value, e.g., ${myvar=some default value}
  • Enhancement: recompiled linux agents for wider libc compatibility
  • Removed: obsolete kwatee ant plugin (can use python commands instead)
  • Minor UI improvement with variable names length
  • Bug fix: ignore integrity check on overlay incorrectly saved as ignore variables in server overlays
  • Bug fix: removed incorrect error message after uploading overlays in Chrome

New in version 2.2.1 (July 15th, 2014)

  • Fixed regression with linux_64 agent
  • EC2 regression fixes

New in version 2.2.0 (June 3rd, 2014)

  • New: H2 embedded db. This is now the default configuration defined in kwatee.properties
  • New: command-line deployer. Enables deployment to multiple servers within a datacenter with a command line application and a deployment archive.
  • New: ZooKeeper server pool add-on, courtesy of ... (separate download)
  • Enhancement: user interface improvements
  • Enhancement: encrypt server passwords and private keys
  • Enhancement: added REST operation to update snapshot variables
  • Enhancement: added REST operation to retrieve list of environments & releases
  • Enhancement: added REST operation to retrieve list of artifacts & versions
  • Enhancement: improved interface for 3rd party server pool implementations
  • Enhancement: server passwords are encrypted in db
  • Enhancement: support password-protected private keys, including password prompt
  • Enhancement: configurable file extensions black list for kwatee variable scanning
  • Enhancement: highlighting of kwatee variables when browsing archive files
  • Enhancement: kwatee variable pattern can be customized to scan variables within archive files/overlays. Default remains '%{varName}'
  • Enhancement: inline default values for kwatee variables (e.g. %{myvar=test})
  • Enhancement: improved compatibility with latest zip formats
  • Enhancement: native win64 platform support resolves issues with some powershell scripts when running in 32bit mode
  • Info: renamed the 'package' concept to 'artifact'
  • Info: renamed the 'deployment' concept to 'release'
  • Info: renamed the 'SKETCH' deployment to 'snapshot' release
  • Bug Fix: prompt for password on deploy
  • Bug Fix: delete overlays when uploading archive now works

New in version 2.1.18 (April 18th, 2014)

  • Bug Fix:
  • windows offline installer deployment actions are now correctly executed
  • removed legacy limitation on deployable number of servers per release
  • empty directories in archives are now supported

New in version 2.1.17 (March 11th, 2014)

  • Bug Fix: "The agent for this platform is not installed" error with solaris_sparc servers.

New in version 2.1.16 (December 10th, 2013)

  • Bug Fix: newly created Amazon EC2 pool generates a 500 error
  • Bug Fix: issue with zip files containing a single entry which showed as empty
  • Bug Fix: system variable override not working properly in frozen deployment

New in version 2.1.15 (November 27th, 2013)

  • Bug fix: error in mysql db upgrade script (apologies)