Release 2016.08

Initial version
In this release webserver calls can be made that invoke shell scripts.
We needed to have a solution that Jenkins had to invoke shell scripts on the remote server, but only to predefined ones. The shell scripts were created and deployed to the remote server by the team. A naming convention was agreed upon for the scripts.
Shell script naming conventions
.sh
Where and could basically be anything, e.g.:
values could be db2, oracle, idq, powercenter, dac. These values are not enforced by the servlet logic.
values could be artifact (the shell script would then generate a deployable artifact) or deploy

usage
The URL for the servlet follows the following syntax:
http(s)://:/ConsagDeployer/artifacts?type=&action=
For example, the following URL would call a shell script db2artifact.sh that creates a db2 artifact.
http://our_remote_server:8080/ConsagDeployer/artifacts?type=db2&action=artifact

Obviously the db2artifact.sh would need to exist, be executable and actually generate a deployable db2 artifact.

dependencies
The war deployment has been tested on Jetty 9.3.8 running with a JDK1.8 64bit (OpenJDK)
All code compiled with JDK 1.8