Sprint 231 (Team B)

[l0rd]

This issue collects work items of the Eclipse Che https://github.com/eclipse/che/labels/team%2FB for Sprint 231 (January 25th - February 14th) (three weeks).
📓 Please note that this is a tentative plan until sprint planning has been conducted (January 25th)

Sprint goals

• Release Che 7.60 (ETA Jan 25-26)
• Release Dev Spaces 3.4.0.GA (ETA Feb 6-7)
• Mention, in che-incubator org, that Eclipse Che is a registered trademark of the Eclipse Foundation #21944

Sprint backlog

https://github.com/eclipse/che/labels/area%2Fdevfile-spec

• no tasks for this sprint

https://github.com/eclipse/che/labels/area%2Fdevworkspace-operator

• Add tests for DevWorkspaceRouting devfile/devworkspace-operator#996
• Use projected volumes for automount configmaps/secrets when they use the same mount path devfile/devworkspace-operator#1021
• Starting workspaces from a Dockerfile #21187
• Merging container contributions can break commands/events devfile/devworkspace-operator#1029
• DevWorkspaceRouting reconciler breaks endpoints when they specify a path devfile/devworkspace-operator#1031

Web terminal operator

• Process Web Terminal Operator v1.7.0 downstream release
• Improve and simplify the Web Terminal Operator release process
• Support for persistent storage per user

https://github.com/eclipse/che/labels/area%2Feditor%2Fvscode

• https://issues.redhat.com/browse/CRW-3529
• Verify VS Code WebView functionality in a disconnected environment
• Help the Prod. Team with the Cachito-based build of VS Code CRW-3160
• To start VS Code, use post-start rather than overriding the entrypoint #21879
• Remove the DevWorkspace handler code from the Che-Code repository #21837
• Document the known issues related to cookie blocking by different browsers #21853
• Allowing users to update the workspace if they edit the project devfile in VS Code #18670
• Implementing a VS Code walkthrough extension for the creation of Devfiles
• Github actions fail for Che-Code on the downloading ripgrep step #21982
• Adapt Che-Code to the latest VS Code upstream changes #21984
• sync-to-downstream job fails for VS Code

https://github.com/eclipse/che/labels/area%2Feditor%2Fjetbrains

• Investigate the possibility of integration with JetBrains Gateway #21412
• Inject JetBrains in the devfile tooling container (as for VS Code) #21878

https://github.com/eclipse/che/labels/area%2Fudi

• Support "podman run" from within a workspace
• https://issues.redhat.com/browse/CRW-3249
• Add an upstream UDI based on UBI9
• CRW-3865 include sdkman in downstream UDI container
• CRW-3072 include jbang binary in Universal Developer image

https://github.com/eclipse/che/labels/area%2Fqe + https://github.com/eclipse/che/labels/e2e-test%2Ffailure +

• CRW-3893 Automate test for checking the predefined DevSpace testflow
• CRW-3669 Run test case 'Empty workspace sample E2E GUI test' on x86_64 OCP 4.10, OCP 4.12, airgap OCP 4.12
• CRW-3675 Run test case 'NodeJS MongoDB devfile API test' on x86_64 OCP 4.10, OCP 4.12, airgap OCP 4.12
• CRW-3725 Run test case 'GitHub Enterprise Server: private repo factory with accepted OAuth' on x86_64 OCP 4.10, OCP 4.12
• CRW-3763 Run test case 'DS install load tests on real-world infra'
• CRW-3727 Run test case 'GitHub Enterprise Server: private repo factory with refused OAuth' on x86_64 OCP 4.10, OCP 4.12
• CRW-3728 Run test case 'GitHub Enterprise Server: private repo factory with no OAuth or PAT' on x86_64 OCP 4.10, OCP 4.12
• CRW-3729 Run test case 'GitHub Enterprise Server: public repo factory with accepted OAuth' on x86_64 OCP 4.10, OCP 4.12
• CRW-3731 Run test case 'GitHub Enterprise Server: public repo factory with refused OAuth' on x86_64 OCP 4.10, OCP 4.12
• CRW-3732 Run test case 'GitHub Enterprise Server: public repo factory with no OAuth or PAT' on x86_64 OCP 4.10, OCP 4.12
• CRW-3655 Create typescript GUI test script which verifies creation of workspace from BitBucket factory URL with Che Code editor
• CRW-3761 Run test case 'Custom Che Plugin registry'
• CRW-3883 Typescript E2E factory test failed: "TimeoutError: Waiting for element to be located By(xpath, .//a[@title='Commit Changes'])"
• CRW-3917 'Factory.spec.ts' E2E test failed when checks 'Push the changes'

https://github.com/eclipse/che/labels/area%2Fci + https://github.com/eclipse/che/labels/kind%2Frelease +

• Release Dev Spaces 3.4.0.GA (ETA Feb 6-7)
• Release Che 7.60 (ETA Jan 25-26)
  • Set set provenance:false in workflows with docker/build-push-action (remove 0.9.1 pin in use docker/setup-buildx-action) #21954
• CRW-3879 automate creation of PNC version/job when creating a new release - Mykhailo
• CRW-3336 pluginregistry :: Use fetch-artifacts for plugin registry build assets - Sam
• CRW-3805 update devspaces-samples projects when releasing DS to force-push a main branch w/ the latest release
• CRW-3581 enable github to jira integration (openshift-ci)
• 39 restricted dependencies used in che-code and code-rhel8 container builds #21931
• Tech debt: devfilev2 and master branch cleanup in che-samples repos #21926
• Deduplicate samples between che-samples and devspaces-samples #21586

[AObuchow]

Some DWO issues:

• Add tests for DevWorkspaceRouting devfile/devworkspace-operator#996
• Use projected volumes for automount configmaps/secrets when they use the same mount path devfile/devworkspace-operator#1021

[azatsarynnyy]

Editors-related suggestion:

• Investigate the possibility of integration with JetBrains Gateway #21412
• To start VS Code, use post-start rather than overriding the entrypoint #21879
• Inject JetBrains in the devfile tooling container (as for VS Code) #21878
• Remove the DevWorkspace handler code from the Che-Code repository #21837

[nickboldt]

Prod - Team B assignments:

• CRW-3879 automate creation of PNC version/job when creating a new release - Mykhailo
• CRW-3336 pluginregistry :: Use fetch-artifacts for plugin registry build assets - Sam

Prod Backlog B:

• CRW-3805 update devspaces-samples projects when releasing DS to force-push a main branch w/ the latest release
• CRW-3581 enable github to jira integration (openshift-ci)
• 39 restricted dependencies used in che-code and code-rhel8 container builds #21931
• Tech debt: devfilev2 and master branch cleanup in che-samples repos #21926
• Deduplicate samples between che-samples and devspaces-samples #21586

[azatsarynnyy]

And one more candidate for the sprint https://issues.redhat.com/browse/CRW-3885

[nickboldt]

3 more candidates for this sprint: https://issues.redhat.com/browse/CRW-3628?jql=filter%20%3D%20%27crw_freeze%27%20and%20filter%20%3D%20%27crw_unresolved%27%20and%20(labels%20not%20in%20(%27releasework%27)%20or%20labels%20is%20empty)%20and%20type%20!%3D%20%27QE%20Task%27%20AND%20component%20not%20in%20(testing%2C%20docs)%20and%20summary%20!~%20%27RN%27 (issues with fixversion = 3.4.0, but not resolved)

and two UDI issues, for this/next sprint:

• CRW-3865 include sdkman in downstream UDI container?
• CRW-3072 Include jbang binary in Universal Developer image

[nickboldt]

Another item for this sprint #21954 was found during the 7.60 release.

[azatsarynnyy]

I added a couple of unplanned items (VS Code-related):

• Github actions fail for Che-Code on the downloading ripgrep step #21982 (it used to be a minor one until I knew it impacts the release. Thanks @nickboldt for rising that problem!)
• Adapt Che-Code to the latest VS Code upstream changes #21984 (to unblock the auto-rebase against upstream)
• sync-to-downstream job fails for VS Code (impact: DS 3.5 build)

Both are simple, but really important fixes.
cc @l0rd

[nickboldt]

Continued in #22001