search

eclipse-archived / codewind

The official repository of the Eclipse Codewind project
https://codewind.dev
Eclipse Public License 2.0
113 stars 45 forks source link

Allow experimental appsody extensions to show up in codewind for testing #366

Open sghung opened 5 years ago

sghung commented 5 years ago

Codewind version: 0.3.0 OS: Mac

Description of the enhancement: Right now, experimental appsody stacks do not show up. However, to ensure we know what projects may go to incubator, we should test any new ones and open issues if we find them

Proposed solution: Add an environment variable to enable experimental appsody stacks

sghung commented 4 years ago

Already implemented. Experimental Appsody extensions can be added to 0.7.0

sghung commented 4 years ago

Need to re-open, I had used the URL: https://github.com/appsody/stacks/releases/download/nodejs-functions-v0.2.0/experimental-index.json instead of the default one https://github.com/appsody/stacks/releases/latest/download/experimental-index.yaml which does not work. Thanks to Andrew for pointing this out

makandre commented 4 years ago

But you do have a simple workaround there for getting experimental repos in Codewind; using a different URL.

neeraj-laad commented 4 years ago

What is the process for adding the experimental repo while using CodeWind? I can see why that is not enabled by default, but I hope the process for enabling it is simple and straight forward.

makandre commented 4 years ago

Hi @neeraj-laad, in earlier releases of Codewind, our SVT was encountering a lot of problems with testing stacks in experimental repo and hence it was decided we would hide the experimental repo by default.

As of now, the only way to add the experimental repo is to use the workaround mentioned above; i.e add it using a different (not latest) url. This enhancement is about having a formal way to unhide the hidden experimental repo.

rtaniwa commented 4 years ago

@neeraj-laad out of curiousity...why are there three separate files for each stack type? Why wouldn't there be a single json file that labels if the stack is experimental, stable, or incubator? The method to add experimental to Codewind seems very clunky, but part of it appears to be because of how there are different indexes rather than one master one.

sghung commented 4 years ago

I discussed this issue more with @makandre, the simplest workaround is to tell the user to add the experimental repo (e.g. https://github.com/appsody/stacks/releases/download/nodejs-functions-v0.2.0/experimental-index.json) instead of the official one (https://github.com/appsody/stacks/releases/latest/download/experimental-index.json). This will ensure things sync properly.