Deployment version control

Context

• When deploying a service using the java-server, if it was deployed in the same place before, then a snapshot should be created and the deployment should be replaced.
• No manual steps should be taken to re-deploy a service.

What was done

• If a state file already exists, we copy the external files into the installation directory and compress it in place.
• We create a checksum to ensure no manual change was done after.
• We delete the previous installation.

TODO

• Another task will provide the rollback step (just uncompress, copy files to correct place and run), to simplify the reviews these will be done in a separate task.
• Once the rollback is done, add a last step to rollback automatically if the deployment fails? To be discussed.
• What to do if we install in a different directory? Currently we have the version in the path, meaning every version will be a different path... To be discussed with POs and reviewers.

QA

• PM data collector has been deployed and redeployed in mpenode3 and behaves correctly.

Review objectives

• Assessment of code functionality
• Assessment of code quality
• Identifying potential refactorings / logic common to other projects
• Knowledge sharing
• Getting help to decide what to do in edge cases