Skip to content
This repository was archived by the owner on Oct 12, 2022. It is now read-only.

Add CODE_EXTENSIONS_PATH env var#71

Merged
bpasero merged 1 commit intomicrosoft:masterfrom
vazexqi:add-code-extensions-path-env-var
Jul 3, 2017
Merged

Add CODE_EXTENSIONS_PATH env var#71
bpasero merged 1 commit intomicrosoft:masterfrom
vazexqi:add-code-extensions-path-env-var

Conversation

@vazexqi
Copy link
Contributor

@vazexqi vazexqi commented Jul 1, 2017

This allows us to also point to a folder with all the extensions that need to be part of the tests (for integration/systems types tests).

I'll open another PR for updating https://code.visualstudio.com/docs/extensions/testing-extensions#_running-tests-automatically-on-travis-ci-build-machines to include the new env var.

Resolves #70.

This allows us to also point to a folder with all the extensions that need to be part of the tests (for integration/systems types tests).
@bpasero bpasero merged commit 64f851d into microsoft:master Jul 3, 2017
@bpasero
Copy link
Member

bpasero commented Jul 3, 2017

Thanks

vazexqi added a commit to forcedotcom/salesforcedx-vscode that referenced this pull request Jul 3, 2017
I submitted two PRs to allow for the tests to specify an extensions folder as well.

microsoft/vscode-extension-vscode#71
microsoft/vscode-docs#1063
vazexqi added a commit to forcedotcom/salesforcedx-vscode that referenced this pull request Jul 3, 2017
I submitted two PRs to allow for the tests to specify an extensions folder as well.

microsoft/vscode-extension-vscode#71
microsoft/vscode-docs#1063
@vazexqi vazexqi deleted the add-code-extensions-path-env-var branch July 14, 2017 20:12
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants