Checks in ReleaseTools::Services::PackageStatus run in parallel for each tag
What does this MR do and why?
Checks in ReleaseTools::Services::PackageStatus run in parallel for each tag to speedup fixing at urgent time.
Development based on issue.
The main goal is to get results (failed validations) for all tags after a single pipeline run. This behavior will speed up troubleshooting in case more than one tag fails validation.
Content
- Checks in ReleaseTools::Services::PackageStatus run in parallel for each tag
Author Check-list
-
Has documentation been updated?