Skip to content
🚀 Deploy to OpenShift

Fix DB_NAME conflict #16

Sign in to view logs

Fix DB_NAME conflict

Fix DB_NAME conflict #16

Triggered via push September 9, 2024 17:16
@warrenchristian1teluswarrenchristian1telus
pushed 34db96b
e66ac2-prod
Status Startup failure
Total duration –
Artifacts –

build.yml

on: push
📋 Environment Check
📋 Environment Check
🔨 Build App  /  🐸 Build to JFrog
🔨 Build App / 🐸 Build to JFrog
🔨 Cron  /  🐸 Build to JFrog
🔨 Cron / 🐸 Build to JFrog
🔨 DB  /  🐸 Build to JFrog
🔨 DB / 🐸 Build to JFrog
🔨 PHP  /  🐸 Build to JFrog
🔨 PHP / 🐸 Build to JFrog
🔨 Web  /  🐸 Build to JFrog
🔨 Web / 🐸 Build to JFrog
🚀 Deploy  /  deploy
🚀 Deploy / deploy
🧹️ Clean-up  /  OpenShift
🧹️ Clean-up / OpenShift
🚦 Audit
🚦 Audit
📫 Notify
📫 Notify
Fit to window
Zoom out
Zoom in

Annotations

1 error
Invalid workflow file: .github/workflows/build.yml#L173
The workflow is not valid. In .github/workflows/build.yml (Line: 173, Col: 11): Error from called workflow bcgov/performance/.github/workflows/deploy.yml@34db96b4fbb86503842e7b2b3585eceed9691f68 (Line: 160, Col: 11): 'DB_POD_NAME' is already defined In .github/workflows/build.yml (Line: 173, Col: 11): Error from called workflow bcgov/performance/.github/workflows/deploy.yml@34db96b4fbb86503842e7b2b3585eceed9691f68 (Line: 178, Col: 11): 'DB_POD_NAME' is already defined