CI jobs to test OTB initialization/installation

Description

When doing the modularisation, I encounter different problem during otb installation on L0_modules with packets generated by CI. As we (the developers) are mainly testing our work with a compiled OTB version, the generated otbenv.profile and other cmake files can slightly differ from the ones generated by CI. Thus the initialization scripts generated by CI are not tested and bugs can be discovered by users.

We can add 3 jobs (Ubuntu different from the one generated the package, RedHat, Windows) testing two differents installation cases:

  • The installation the all-in-one package
  • The installation with only Core and dependency (not available for Windobe)

We can use the packages generated previously by the build job available in artifacts. The installation should be a in different folder that the one use for build (to detect cmake path errors)

Definition of Ready

Generic:

  • If this issue is consequent, it is split into subtasks with priority and complexity evaluated. These subtasks should be linked to this issue. (To do on GitLab interface after writing this issue)
  • Issue complexity evaluated
  • Priority of issue evaluated
  • If there is a specific documentation/specification need, it should be available to the development team
  • Time during the sprint to realize this issue

Specific:

Definition of Done

Generic:

  • No test regression on CI
  • Code reviewed by peers
  • Code cleaned, no "debug" traces or "TODO" comments kept.
  • New code documented

Specific:

  • Ubuntu job to test complete and modular package installation. Version must be different that the one used to publish package
  • RedHat job to test complete and modular package installation
  • Windows job to test complete installation (modularity not available)