WildFly v2.0.1 stack sample fails to build and deploy

[olexii4]

Which area this feature is related to?

/kind bug

Which area this bug is related to?

/area registry

What versions of software are you using?

Web browser

Operating System and version: macOS Sonoma 14.4 Browser name and version: Google Chrome v122.0.6261.129

Bug Summary

Describe the bug:

Create a new workspace from java-wildfly 2.0.1 stack with Che. A workspace is created successfully, but some commands don’t work (Containerfile and .charts/helm.yaml couldn’t be found).

To Reproduce: Opening the URL https://workspaces.openshift.com#https://raw.githubusercontent.com/devfile/registry/main/stacks/java-wildfly/2.0.1/devfile.yaml in your browser should start a workspace. Build and deploy commands run unsuccessfully.

Expected behavior

Opening the URL https://workspaces.openshift.com#https://raw.githubusercontent.com/devfile/registry/main/stacks/java-wildfly/2.0.1/devfile.yaml in your browser should start a workspace where all exec commands run successfully.

Any logs, error output, screenshots etc? Provide the devfile that sees this bug, if applicable

Additional context

Any workaround?

Suggestion on how to fix the bug

[thepetk]

@olexii4 FYI the https://github.com/devfile/registry/pull/368 was opened by @ehsavoie in order to fix the container file issue.

[thepetk]

A question is if the devfile.yaml is accessible inside the workspace, so for example someone can change the variables inside the devfile

cc @olexii4

[olexii4]

@thepetk In the case when a new workspace is created from a stack, devfile.yaml is not accessible inside the workspace.

We can restart the workspace from the local devfile.yaml. It will be useful to add the target devfile into the repository too.

[ehsavoie]

I added the devfile in the starter project