Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lagoon Build Errors pages #3608

Merged
merged 4 commits into from
Dec 1, 2023
Merged

Lagoon Build Errors pages #3608

merged 4 commits into from
Dec 1, 2023

Conversation

tobybellwood
Copy link
Member

@tobybellwood tobybellwood commented Nov 30, 2023

This PR adds a dedicated page for Lagoon Build errors, and two "short URLs" for use in Lagoon Builds that point to it

We can add more errors that we trap in Lagoon Builds as needed.

@shreddedbacon
Copy link
Member

Maybe call it Errors and Warnings?

@AlannaBurke
Copy link
Contributor

I like this, I think Ben's suggestion is good. Also, maybe give some more detailed examples? You wrote "The error message should help you understand where." - would it be possible to put an example where that happens?

I think we should add something at the top like "Here are some common errors and warnings you may encounter and how to resolve them. If you need help with your build, please reach out to your Lagoon admin or reach out on Discord for community help."

@shreddedbacon
Copy link
Member

The error message should help you understand where.

For those ones in particular, the build itself will spew out the warning/error message and the appropriate remediation strategy and where it went wrong. This could be different depending on the way the user has done their docker-compose or .lagoon.yml file so it would be difficult to give concrete examples, but not impossible.

@tobybellwood tobybellwood added this to the 2.17.0 milestone Nov 30, 2023
@tobybellwood tobybellwood merged commit 8e7272e into main Dec 1, 2023
1 check passed
@tobybellwood tobybellwood deleted the docs/docker-compose branch December 1, 2023 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants