-
Notifications
You must be signed in to change notification settings - Fork 3
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
Fix codebuild build #235
Fix codebuild build #235
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about good commands to run elara in container, maybe something from a matesto pipeline?
you could run smoke tests? |
@KasiaKoz I don't know why I didn't think of using Matesto for smoke testing this new Elara image in a pipeline, but that's exactly what I should have done. Anyway, I did it, and all was well: ![]() ![]() |
I forget about matesto too sometimes 😭 |
@fredshone good suggestion. I ran the smoke tests inside a container launched from the new Docker image (BTW the smoke test script must be run with ![]() |
You'd think I'd remember it though, eh? 🤦 |
The Problem
Although the Docker image builds locally, it has been failing consistently in CodeBuild for over a week in a way that I have been unable to reproduce outside of CodeBuild. The errors looked exactly like the ones described here, even though that is a CircleCI build rather than CodeBuild.
The Solution
Also as described here, the solution was to switch to a different base image from the same provider.
Validation of the Solution