Windows CI Integration #702
Conversation
|
|
||
| - pwsh: | | ||
| if ("$(TESTKIND)" -eq "unit") { | ||
| go test -v -parallel 1 $(go list ./... | where-object { $_ -notlike "*/test" }) | Tee-Object -FilePath 'logs/unit.log' |
There was a problem hiding this comment.
I think we normally use run-go-test for this, which sets other options, such as -timeout. Can you make sure we re-use those here?
Also, perhaps a dumb question, but is there no way we can reuse any of those Bash scripts here? I'm curious if we can reduce duplication at all between Windows and *nix.
There was a problem hiding this comment.
I can run it on "Bash for Windows" (https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema#bash). The problem with this approach is, the tests will still be running in the linux subsystem and not on Windows directly. That negates the whole point of setting up a Windows CI
There was a problem hiding this comment.
Should we use python for our CI scripts once we have more windows CI tasks, to avoid the code duplication?
There was a problem hiding this comment.
Yea, probably. I mean, that still requires Python to be installed, and there will still be other OS differences to paper over (e.g., path lengths), but that should help.
There was a problem hiding this comment.
At least it isn't "share no code" 😄
There was a problem hiding this comment.
Why not Golang? Installing Python is going to be a mess, someone's bound to install something and complain...
| } | ||
|
|
||
| if ("$(TESTKIND)" -eq "integration") { | ||
| go test -v $(go list ./... | where-object { $_ -like "*/test" }) | Tee-Object -FilePath 'logs/integration.log' |
| displayName: 'Run `dep ensure`' | ||
|
|
||
| - pwsh: | | ||
| if ("$(TESTKIND)" -eq "unit") { |
| } | ||
| workingDirectory: '$(modulePath)' | ||
| displayName: 'Run tests' | ||
| continueOnError: true |
There was a problem hiding this comment.
We need this here so that the task that publishes the xml test results will run. The entire build pipeline is still marked as failed so it doesn't change much
| $(system.defaultWorkingDirectory)\terratest_log_parser.exe --testlog logs/integration.log --outputdir ./logs/integration/ | ||
| } | ||
| workingDirectory: '$(modulePath)' | ||
| displayName: 'Generate Test Report' |
|
@brikis98 I invited you to the Gruntwork Azure DevOps org. Let me know if you have any trouble |
|
Just checking if this is something we're still interested in. So I can properly handover ownership of the Azure DevOps Gruntwork organization |
|
Any update on this? Building out a pipeline and wondering; when this is going to be merged? |
This PR sets up a Windows CI for Terragrunt using Azure Pipelines (replacing AppVeyor).
We're able to split into unit and integration test jobs
We can also publish XML test results generated by the Terratest log parser
Unlike AppVeyor (and like CircleCI) we can have organizations
Some tests are failing of course, but the point of this PR is to get the Windows CI infrastructure setup