Use Universal Developer Image as dev container

[vitaliy-guliy]

What does this PR do?

• Inherits che-code-dev image from Universal Developer Image
• Adds few commands to build che-code image with podman

What issues does this PR fix?

eclipse-che/che#22292

How to test this PR?

Do following:

• use the dogfooding instance to create a workspace from the current branch https://github.com/che-incubator/che-code/tree/switch-to-udi
• use devfile commands to compile and run VS Code with yarn
• use devfile commands to compile and then build che-code image with podman

Should have like following:

---

Note that:

• all the 30 commits will be squashed when merging. I haven't squashed them here because of 1) all the commits to the branch were performed using online che-code, as for me the squashing it not clear UX flow; 2) do not want to add an extra commit as it triggers the github PR checks

• at the moment, quay.io/che-incubator-pull-requests/che-code-dev:pr-246-dev-amd64 is used as a dev image. I plan to update it after merging of this pull request and when the corresponding che-dev image will be built by the appropriate github action.

[github-actions]

Click here to review and test in web IDE:

[vitaliy-guliy]

There is one thing that needs to be fixed - is optimize the dev image as its size a bit huge

$ docker images
REPOSITORY                                  TAG                  IMAGE ID       CREATED         SIZE
quay.io/vgulyy/che-code-dev                 next-udi             7610232c9b24   25 hours ago    9.63GB

[RomanNikitenko]

universal-developer-image has a lot of tools, but as result it has a huge image size
is it really required to have all those tools from the universal-developer-image for the che-code development?
can we just add required tools to the dev image?

just for my understanding, as you are working on it and you know the problem better then me...

[vitaliy-guliy]

I had some issues with configuring the podman in current che-dev image.
So, It was much easier to take the universal developer image and add missing libraries, required for building vscode.

[azatsarynnyy]

@vitaliy-guliy I believe the GitHub Workflow-related changes deserve a separate PR. As they are not directly related to the current PR. However, the current PR depends on these changes. We can review/test the GitHub Workflow simplification separately.

[vitaliy-guliy]

@vitaliy-guliy I believe the GitHub Workflow-related changes deserve a separate PR. As they are not directly related to the current PR. However, the current PR depends on these changes. We can review/test the GitHub Workflow simplification separately.

This pull request

• introduces the changes into che-code-dev image
• adapts pull request chesks to those changes.

Here I removed two existing jobs with messy logic (we discussed that) and added two separate independent jobs to build che-code and che-code-dev images.

[azatsarynnyy]

With the help of matrix strategy, you can combine Compile linux-libc and Compile linux-musl steps into just a single step.

[vitaliy-guliy]

I reworked it intentionaly to prevent storing somewhere (uploading artifacts) the result of two launches of the build job.
Now we do not store artifacts. Now we build libc and musl, then build che-code image, upload it to quay.io and forget.

[github-actions]

Pull Request Che-Code image published:
👉 quay.io/che-incubator-pull-requests/che-code:pr-246-amd64

[github-actions]

Pull Request Dev image published:
👉 quay.io/che-incubator-pull-requests/che-code-dev:pr-246-dev-amd64

[github-actions]

Pull Request Che-Code image published:
👉 quay.io/che-incubator-pull-requests/che-code:pr-246-amd64

[vitaliy-guliy]

Superseded by #253