How to install Nightly version of Docker extension

[bwateratmsft]

The latest nightly build of the Docker extension can be installed by anybody. To do so:

1. Download the VSIX from the "Published Artifacts" link here (in the vsix artifact, looks like vscode-docker-1.26.0.vsix):

2. In VSCode, open the command palette (F1 by default) and type "Extensions: Install from VSIX...", hit enter
3. It will open up a file picker; choose the downloaded vscode-docker-x.y.z.vsix. The extension will be installed and may require a reload of VSCode.

For more information on installation, see here: https://aka.ms/azCodeInsiders

[eine]

IMHO, this content might better fit in the README, instead of being an issue.

[philliphoff]

@eine Point taken but, if I remember correctly, we explicitly decided not to add it to the README.md, as that file is used verbatim in the VS extension marketplace and we didn't want to potentially confuse users by having instructions for installing the nightly alongside the official extension installation process. I'd expect most users wishing to install a nightly are doing so to test an update related to an issue they've submitted, hence keeping the instructions close to the Issues page.

[eine]

@philliphoff, that's a fair point, but I believe that the current solution is falling short to achieve it. Users that are wishing to install some nightly to test an update related to an issue, are unlikely to want the version that is linked in the shield/badge above. Conversely, they should go to the PR they want, check the tests/checks/jobs of that specific PR and get the artifacts from there. I'm saying this because I have done it several times before.

Therefore, I think that a good compromise is to move the content from this issue to a markdown file in the codebase. Then, that file can be linked from the "Contributing" section of the README, from this pinned issue and/or from any other place where it might be useful (whenever a user asks how to test a specific feature which is WIP).

[bwateratmsft]

Was hoping that locking would prevent unpinning.

[bwateratmsft]

Maybe replace this with an Insiders build of the extension: microsoft/vscode#15756 (comment)

[bwateratmsft]

Maybe replace this with an Insiders build of the extension: microsoft/vscode#15756 (comment)

I looked and we have at most 3 external users with a nightly build installed, and odds are at least some of those 3 are actually internal. IMO the interest just is not there, not enough to justify working on a proper version using the new pre-release extension feature.

[wsmelton]

If you cannot consider using the preview extension option at this time, at least publish it as a release on GitHub with the pre-release tag. I would prefer to have VS Code Insider release since I use that as my day-to-day for just this purpose. Either way, if it was available as a pre-release tag on GitHub it is easier to consume and automate on my own to pull it down each day and install.

[bwateratmsft]

I think we should take another look at using VSCode's preview release feature. At the time this issue was authored it didn't exist, but I think it's a good fit. I'm going to remove the milestone from this issue so we can retriage it.

[dbreshears]

Not planned