-
Notifications
You must be signed in to change notification settings - Fork 13
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
Sandbox test environment #2941
Sandbox test environment #2941
Conversation
MDrakos
commented
Dec 12, 2023
•
edited by github-actions
bot
Loading
edited by github-actions
bot
DX-2285 Our integration test environment is completely sandboxed |
Debug path appending
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.
This looks quite good overall, with my only real concern being that it might be too finely-tuned for running on GitHub Actions CI that it might not run on our systems locally (at least for Windows).
.github/workflows/build.yml
Outdated
@@ -106,6 +105,13 @@ jobs: | |||
run: | | |||
echo "${PSScriptRoot}/.github/deps/${{ runner.os }}/bin" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append | |||
|
|||
- # === Setup Windows === | |||
name: Debug (Windows) |
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.
Did you mean to leave this block in? If not, can we just revert all changes from this file? I'm a bit nervous with the quoting changes on lines 267 and 292 below.
.github/workflows/build.yml
Outdated
@@ -258,7 +264,7 @@ jobs: | |||
|
|||
- # === Deploy for Integration Tests # NEVER run this against production branches. This is meant for PR deployments. === | |||
name: Deploy for Integration Tests # NEVER run this against production branches. This is meant for PR deployments. | |||
if: "!contains(fromJSON('[\"refs/heads/beta\", \"refs/heads/release\", \"refs/heads/LTS\"]'), github.ref)" | |||
if: '!contains(fromJSON(''["refs/heads/beta", "refs/heads/release", "refs/heads/LTS"]''), github.ref)' |
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.
Is this really allowed? It has me worried, because it doesn't look syntactically valid.
@@ -0,0 +1,37 @@ | |||
//go:build windows |
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.
Have you tried running e2e tests locally with these changes? The variables defined here may be too finely-tuned for GitHub Actions CI.
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.
Yes, they ran fine on my local machine. We also can disable the sandbox with an env var if it's a problem. I expect there to be some issues with this and we can change it to opt-in as well as fine-tune the sandboxing if/when issues pop up.
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.
Oh and as for the env vars on Windows they appear to be fairly standard, except for the msys one which should not only be prepended when on CI.
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.
Excellent work. I know this was a major pain, but kudos for sticking with it!
Test failures should be unrelated to this PR |