-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Provide access to native binaries for CI testing #8691
Comments
@microsoft/embedded-dev is also interested in whatever approach you come up with to share these files. It's currently impacting our automated testing, but for now we have an easy workaround by pinning to 1.8.1. |
We found published |
@EricHripko Are you able to just get the .vsix from the marketplace (https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools)? If necessary, it seems like you could also self-host that somewhere. The only thing we stopped doing is uploading the vsix's on our Releases page (to minimize our manual release process steps). |
Note that this issue is tracking providing internal builds of Users who want to clone the repo should use the |
Ah sorry for my misinterpretation of this issue @Colengms. I'm happy to submit a new issue if that's desired. @sean-mcmanus I seem to be able to download the VSIX from |
@EricHripko Were you interested in the latest Pre-Release/Insiders (i.e. 1.9.1) or the latest Release (i.e. 1.8.4)? |
@sean-mcmanus the latter (latest stable release). |
We post a page for the latest stable release as https://github.com/microsoft/vscode-cpptools/releases/latest , which currently resolves into https://github.com/microsoft/vscode-cpptools/releases/tag/1.8.4 , even though it doesn't have any vsix attachments. Are you able to query that to get the latest 1.8.4 version to use in the marketplace URLs? |
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.
The text was updated successfully, but these errors were encountered: