Verify build / test / package / release scripts/tasks work on Windows
See original GitHub issueThere are lots of parts of the build / test / package / release process which may depend on UNIX features (e.g. ,bash
, mkdir -p
, etc.) that may not exist on Windows.
Describe the solution you’d like
We should ascertain which of the npm scripts work properly on Windows, fix any which are easy to fix, and document any which work and which do not as well as whatever preconditions are required to make them work (e.g., do you need WSL?)
Describe alternatives you’ve considered
Let would-be Blockly contributors who use Windows fend for themselves.
Additional context
See also #4983 re: npm script documentation.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (7 by maintainers)
Top Results From Across the Web
fix(build): build/test on windows by yamadayutaka ... - GitHub
Test Coverage Confirmed in the following environments. ... Verify build / test / package / release scripts/tasks work on Windows #5000 · Build...
Read more >PublishTestResults@2 - Publish Test Results v2 task
Specifies a name for the test run against which the results will be reported. Variable names declared in the build or release pipeline...
Read more >Review test results - Azure Pipelines | Microsoft Learn
Review continuous test results with a build or release pipeline in Azure Pipelines or Team Foundation Server (TFS)
Read more >Run quality tests in your build pipeline by using Azure Pipelines
Run unit tests locally and then in Azure Pipelines. Add dashboard widgets to visualize test runs ... Fix and verify test failures in...
Read more >Release gates and approvals overview - Azure - Microsoft Learn
Release pipelines enable teams to continuously deploy their ... work item or problem management system before deploying a build to a stage.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @BeksOmega Thank you for your confirmation. I’m considering another solution using Gulp. An updated version of
google-closure-deps
hasn’t been released yet, so I’m creating it in my branch as a draft version.https://github.com/yamadayutaka/blockly/tree/draft/test_tasks
It doesn’t require WSL or Git Bash, so I think it’s easier to get started.
It has also passed testing with GitHub Actions using Windows Runner.
https://github.com/yamadayutaka/blockly/actions/runs/2144051205
No problem at all! I actually wasn’t able to test yet 😕 The device I was attempting to use ran into an npm error I couldn’t resolve. So now I’m trying to upgrade a different device to a version of windows that supports WSL. Will keep you updated!