Skip to content

Request: Add support for --override-build-id flag in the orb #26

@rd-thalles-daniel

Description

@rd-thalles-daniel

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Describe the problem imposed by not having this feature

We are running a parallel automation workflow that sometimes requires a retry when a job fails. When this happens, sending the 'complete' command to the coverage service can result in a 409 error due to ID conflicts. We have validated that using the --override-build-id flag, as documented here: https://docs.qlty.sh/coverage/merging#total-parts-count, would allow us to successfully complete the workflow and submit all test results, even on retries. However, this flag is not currently available via the orb, which limits our ability to robustly handle parallel executions with retries.

Describe the solution you'd like

We kindly request the implementation of the --override-build-id flag in the orb, in alignment with the documentation. This would enable users to specify an override build ID when running their workflows, allowing more resilient and idempotent coverage aggregation especially in scenarios involving workflow retries. If possible, we encourage thoughtful consideration of how this could be integrated in a way that remains easy to use and avoids introducing complexity for other users. A potential drawback could be the need for added documentation or user education regarding when and how to use the flag safely.

Other

Thank you for your attention to this request. We deeply appreciate the engineering effort and the empathy shown in maintaining this orb. We believe this feature would significantly improve reliability for those running parallelized and retried workflows. Please let us know if you need further details or real-world examples from our use case!

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions