Build execution should wait until all services are ready

Issue #15244 open
Jeroen De Raedt
staff created an issue

Currently, Pipelines does not wait until all declared services are up and running before the build execution starts. As a result, a build could fail because a service container was not fully started yet (e.g. a test failed because a database service container had not fully started).

Maybe this should be an optional configurable setting in the YML? This might require user input to define when a service container is considered to be 'ready'.

Comments (4)

  1. Aneita Yang staff
    • changed status to open

    Thanks for the suggestion.

    This is something that we'll need to investigate in more detail. However, the team are currently working on higher priority issues, so it is unlikely that we'll work on this anytime soon.

    In the meantime, I'll open this ticket to see whether this interests other users.

  2. Log in to comment