Spike: CI duration

[ouphi]

Feature #194 After #171, #223

Description

The goal of this Spike is to analyse the duration of CI. Evaluate:

• What are the core factors increasing CI durations
• What test category take more time

The second part is to evaluate solutions to reduce the duration.

Considerations:

• As discussed in https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/pull/1000#discussion_r841413437 it would be good to migrate usages of setup-java action to the gradle-build action. Consider this in the improvement analysis.

Acceptance Criteria

• [ ] A report to understand CI duration is provided.
• [ ] Potential solutions to reduce the duration are evaluated and documented.
• [ ] Working solutions can be proposed and corresponding stories are created.

Tasks

Same as acceptance criteria.

[algattik]

See also https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/840

[algattik]

Should we do this only after #203 , so that we have test report as data source?

[ouphi]

Created this issue: https://github.com/agera-edc/DataSpaceConnector/issues/224

[github-actions[bot]]

This issue is stale because it has been open for 14 days with no activity.

[zeier]

CI times are currently reasonable and don't require further investigation.