microsoft / microsoft/vscode-cpptools
Provide access to native binaries for CI testing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
With the move to platform-specific VSIX's via the marketplace, it's no longer necessary to publish the native binaries as they are no longer downloaded by the extension when first activated. Unfortunately, this also means our CI testing on GitHub no longer has access to those native binaries. Language server integration tests are currently disabled. Opening this issue to track finding an alternative way to provide native binaries that are aligned with the latest version of the code in GitHub, for CI testing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the GitHub CI setup and the currently disabled language server integration tests. Determine how CI can obtain native binaries aligned with the latest GitHub code, then verify that the integration tests can access them and run successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript, vscode
- Domain
- ci-cd, devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100