Description:

• When initiating service containers during a Bitbucket Pipelines build, if one of the service containers fails to start (e.g., due to licensing changes or other issues), the main build fails. However, the main build log does not provide a clear or actionable error message indicating that the failure was caused by a service container issue. This makes troubleshooting difficult for users.

Customer Impact:

• Users may spend significant time diagnosing build failures without clear guidance.
• Important information about service container failures is not surfaced in the main build log, leading to confusion and delays.

Suggested Improvement:

• Enhance the main build log to include explicit error messages when a service container fails to start or encounters a critical error.
• Optionally, provide a notification or summary in the main build log that directs users to the relevant service logs for more details.