Better feedback about failing deploy with DB_INITIALIZE or DB_MIGRATE

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

When users deploy web app using AutoDevOps its likely they use database migration mechanism.

GitLab provides a nice tools for it in way of setting DB_INITIALIZE and DB_MIGRATE variables. However when db setup or db migrate jobs fails it does not provide much of details in GitLab interface. For example production job with invalid DB_INITIALIZE variable has next output:

$ deploy
secret/production-secret replaced
Deploying first release with database initialization...
Release "production" does not exist. Installing it now.
Error: timed out waiting for the condition

Without knowledge of Kubernetes and kubectl its hard to find the real reason behind the failure. As we don't show logs from failed db-initialize or db-migrate kubernetes jobs.