Verify functionality of each sample from devfile.io on Che

[svor]

Is your task related to a problem? Please describe

Since we start using devfile.io as a default registry for Che samples, we have to make sure that everything declared in the devfiles works as expected with a default Che-code editor:

• workspace can start;
• dev container provides all needed tools to work with the sample project;
• all declared commands work as expected;
• check debugging (if it's possible);
• try to run the sample project (if it's possible);
• Check if the devfile has an https endpoint, see: Verify functionality of each sample from devfile.io on Che #22869 (comment) and Update che-docs preview to use https instead of http #22864. This is needed to properly open the application url from the editor's popup on latest version of Chrome browser.

All samples are available on Che dogfooding instance

Here is the list of samples:

Devfile link	Verified	Assigned
.NET 5.0	✔️	@ibuziuk
.NET 6.0	✔️	@ibuziuk
.NET Core 3.1		@vitaliy-guliy
Angular		@vitaliy-guliy
Django	✔️ devfile-samples/python-django-ex#1	@tolusha
Go Runtime	✔️ devfile/registry#357	@tolusha
Laravel	✔️devfile/registry#349	@dkwon17
Maven Java		@azatsarynnyy
Next.js		@RomanNikitenko
Node.js Runtime		@azatsarynnyy
Nuxt.js		@RomanNikitenko
Open Liberty Gradle	✔️devfile/registry#350	@dkwon17
Open Liberty Maven	✔️devfile/registry#351	@dkwon17
Python	✔️ devfile/api#1524	@dmytro-ndp
Quarkus Java	#22906	@vinokurig
React	✔️	@vinokurig
Spring Boot	✔️ devfile/api#1526	@dmytro-ndp
Svelte	✔️	@svor
Universal Developer Image	✔️	@svor
Vert.x Java	in-progress	@artaleks9
Vue	✔️	@artaleks9
WebSphere Liberty Gradle	✔️	@akurinnoy
WebSphere Liberty Maven	✔️	@akurinnoy
WildFly	✔️	@olexii4
WildFly Bootable Jar	✔️	@olexii4

Describe the solution you'd like

In case some problem was detected, need to provide a PR with the fix into https://github.com/devfile/registry.

If it's a problem that required additional investigation, it's better to register an issue where the problem should be described.

Additional context

An example PR that contributed changes to the net 6.0 devfile: devfile/registry#298

[ibuziuk]

PRs for .NET 5 and 6

• chore: use 'https' protocol for .net 5.0 devfile. Update schema to 2.2.0 devfile/registry#312
• chore: use 'https' protocol for .net 6.0 devfile. Update schema to 2.2.0 devfile/registry#298

[svor]

FYI:

• Add library support for devfile schema - version 2.2.1 & version 2.2.2 devfile/api#1454 was resolved and probably we can bump devfile's schemaVersion to 2.2.2 in devfile.yaml files New issue to track Bump up registry support library version devfile/api#1481
• Here is a slack channel to ask any related questions: https://redhat.enterprise.slack.com/archives/C017YDKHQV6

[artaleks9]

Vert.x Java

• workspace runs, but Unable to resolve nonexistent file in the project tree:

• needed tools are provided
• commands:
  -- mvn-package -> build fail:

-- run -> starting, but Application is not available:

-- debug -> launch, but Application is not available:

[artaleks9]

Vue

• workspace runs, but some code lines is highlight red

• needed tools are provided

• commands:
  -- install:
  

  -- build launching, but Application is not available:

[tolusha]

Django

Added recommended extensions and debug configuration
devfile-samples/python-django-ex#1

[tolusha]

Go Runtime

devfile/api#1490

[akurinnoy]

Update stacks/java-websphereliberty/devfile.yaml

Update stacks/java-websphereliberty-gradle/devfile.yaml

[RomanNikitenko]

• Next.js PR
• Nuxt.js PR

[olexii4]

• java-wildfly-bootable-jar PR
• WildFly v2.0.1 stack fails to build and deploy

[dmytro-ndp]

@artaleks9 : about your comment: #22869 (comment)
I have faced the same problem when check Python and Spring Boot devfiles.
Solution: use https endpoints instead of http in devfile, e.g. devfile/registry#367