This is related to https://jira.onap.org/browse/TSC-25

Existing flow

• gerrit commit on the oom repo for a particular component like so, aai - keyed by Issue-ID Jira
• helm-verify jjb jenkins job currently runs - reports +1/-1
• review is merged
• helm verify runs again on master
• no helm deploy

Proposed flow 1

• gerrit commit on the oom repo for a particular component like so, aai - keyed by Issue-ID Jira
• helm-verify jjb jenkins job currently runs - reports +1/-1
• manual magic word "run-helm-deploy" will kick in a helm-deploy jjb job that deploys robot and the particular pod to a 16-32g VM (preconfigured with rancher as a single node) - how? jenkins will run a remote ssh shell to a server using a cached key - a cd.sh script will need to be written - see the 2 pocs below already running
• reports +1/-1 if healtcheck for that component passes after 20 min - parse the logs from jenkins

Proposed flow 2 later

• gerrit commit on the oom repo for a particular component like so, aai - keyed by Issue-ID Jira
• helm-verify jjb jenkins job currently runs - reports +1/-1
• same helm-install jjb job again is automatically triggered and reports back a +1/-1 after 20 min
• based on # of vms - jobs can be parallelized or batched (report -1/1 to the batch - but only 1 are at fault