-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
Yet another round of battling building and testing containers on Windows #966
Conversation
fc3d9d5
to
d78c1c9
Compare
0618b45
to
4aa3299
Compare
Does this actually work?
cc89924
to
db7e51c
Compare
Much pain, much learning. I think this is ready for a quick review. Mostly I learned about agent setup, and may still have some work to do on that, maybe an agent qualifier script that makes sure git works right and all the right tools are installed? |
fb3645e
to
4c60ebe
Compare
.buildkite/test_containers.sh
Outdated
@@ -7,6 +7,12 @@ set -o pipefail | |||
set -o nounset | |||
set -x | |||
|
|||
echo "--- Cleanup docker" | |||
echo "Warning: deleting all docker containers and deleting ~/.ddev/Test*" |
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.
I don't think ~/.ddev/Test* gets deleted, if we're still expecting that to happen.
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.
Great point - It's a copy-from-original-script problem. This script doesn't ever create anything in ~/.ddev, I'll fix that.
I'm probably good with this now, my energy may have run its course again :) |
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.
Hey, we got the green checks! All changes look reasonable to me.
The Problem/Issue/Bug:
We seem to never be able to build and test our containers on WIndows and elsewhere.
Trying again.
How this PR Solves The Problem:
Script and docs (mostly) updates, and agent debugging
Manual Testing Instructions:
Build should run reliably on each testbot, especially windows testbots.