Shared Jenkins library which all ODS projects & components use - provisioning, SonarQube code scanning, Nexus publishing, OpenShift template based deployments and repository orchestration
When the LeVADoc capabilities were disabled and the jira service is enabled in the metadata.yaml there where some exceptions that were rose due to some checks of the templates version.
The version of the templates is expected to be a string, but the user can change it to a number in the metadata.yaml, this generates an error
This pull request fix both problems
When the LeVADoc capabilities were disabled and the jira service is enabled in the metadata.yaml there where some exceptions that were rose due to some checks of the templates version. The version of the templates is expected to be a string, but the user can change it to a number in the metadata.yaml, this generates an error This pull request fix both problems