Better handling of Unit tests in D and DevPreview

[hrcornejo]

• The execution status of all Unit tests, for all components, are reported into Jira.
• The DTR document is generated and contains information that is consistent with Jira.
• When doing a Developer Preview, the Release Manager pipeline fails only at the end of the Finalize Stage.
• When deploying to DEV, the Release Manager pipeline fails at the end of the Build Stage.
• The Release Manager reports the the failure status into its Release Status issue.

[metmajer]

It would be nice, but I am not sure if this implementation will make the requirements. Consider that a component might decide to fail the build after the first failing unit tests. Currently, components are executed in groups with a failFast property. Therefore, after one failing component, the release manager pipeline would fail.

[hrcornejo]

It would be nice, but I am not sure if this implementation will make the requirements. Consider that a component might decide to fail the build after the first failing unit tests. Currently, components are executed in groups with a failFast property. Therefore, after one failing component, the release manager pipeline would fail.

@metmajer added failFast dependent of WIP.
With 2 projects in parallel with this configuration:

Launching a WIP all the stages are executed, doc generated and issues updated in Jenkins (with failing tests in one component):

Launching a 1.1 version to DEV, the pipeline fails after Build:

[metmajer]

@hrcornejo fantastic! Interestingly, in the second example, the pipeline fails, but we don't see that the component failed. I assume this is because the component itself does not throw an exception/error on test failure?

[hrcornejo]

@hrcornejo fantastic! Interestingly, in the second example, the pipeline fails, but we don't see that the component failed. I assume this is because the component itself does not throw an exception/error on test failure?

Right.