Sprint 232 (Team B)

[l0rd]

This issue collects work items of the Eclipse Che https://github.com/eclipse/che/labels/team%2FB for Sprint 232 (Feb 15th - Mar 7th) (three weeks).

Continued from previous sprint #21942

📓 Please note that this is a tentative plan until sprint planning has been conducted (February 15th)

Sprint backlog

• Remove post-stop event from the devfile spec devfile/api#1032
• Document how Developers private configurations should be managed (not in a Devfile) devfile/api#1033

• 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
• If workspace start fails due to timeout, DWO should reference ignored unrecoverable events if present devfile/devworkspace-operator#1041
• Support image components to use Dockerfile as component spec devfile/devworkspace-operator#1036
• Support configuring rolling updates for workspace deployments devfile/devworkspace-operator#1045
• Support ServiceAccount token volume projection #22012 🆕

• 🟣 Process Web Terminal Operator v1.7.0 downstream release
• ⚪ Improve and simplify the Web Terminal Operator release process
• ⚪ Support for persistent storage per user
• ⚪ Set up automatic rebuilds of web-terminal-exec component for WTO 1.5

• Che-Code automatic rebase against upstream VS Code is failed #22037 🆕
• Update the Node.js runtime for Che-Code according to the new upstream requirements #22024 🆕
• 🟣 [CRW-4053] code_3.x build fails on s390x 🆕
• Update the Node.js runtime for Che-Code according to the new upstream requirements #22024 🆕
• ⚪ [CRW-3942] Not possible to install an extension in air-gapped mode 🆕
• ⚪ [CRW-3160] migrate from pkgs.devel lookaside asset files to cachito w/ yarn
• ⚪ VS Code's WebView functionality doesn't work when the browser is behind the proxy
• 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 #21987
• Make Che-Code CI build more stable when downloading artifacts from api.github.com #22003
• Make Che-Code CI build more stable when downloading artifacts from artifacts.electronjs.org/headers #22004

• To start JetBrains IDEs, use post-start rather than overrideing the entrypoint #22034
• Investigate the possibility of integration with JetBrains Gateway #21412
• Inject JetBrains in the devfile tooling container (as for VS Code) #21878

• ⚪ [CRW-3367] Allow running podman from within a workspace
• Universal Developer Image enhancements #20799
• ⚪ [CRW-3865] include sdkman in downstream UDI container?
• ⚪ [CRW-3072] Include jbang binary in Universal Developer image

• 🟣 [CRW-3818] Create typescript GUI test script which verifies scenario when user refuses GitLab oAuth setup during start of workspace using factory URL
• 🟣 [CRW-3809] Create typescript GUI test script which verifies scenario when user refuses BitBucket oAuth setup during start of workspace using factory URL
• 🟣 [CRW-3816] Create typescript GUI test script which verifies factory URL without OAuth and PAT setup
• 🟣 [CRW-3893] Automate test for checking the predefined DevSpace testflow
• ⚪ [CRW-4044] Estimate time of java project build and run inside Che Code Editor in performance tests
• ⚪ [CRW-3936] Create Jenkins job for running Predefined namespace test
• ⚪ Pre-release testing issues
• Create acceptance tests to go through all devfile samples and all editors using API #21514
• Add Che Smoke Test PR check for Che-Code repository #21789

• ⚪

• 🟣 [CRW-3805] update devspaces-samples projects when releasing DS to force-push a `latest` tag w/ the latest release
• Set set provenance:false in workflows with docker/build-push-action (remove 0.9.1 pin in use docker/setup-buildx-action) #21954
• ⚪ [CRW-3336] pluginregistry :: Use fetch-artifacts for plugin registry build assets
• ⚪ [CRW-3581] enable github to jira integration (openshift-ci)
• ⚪ [CRW-4043] Improve process for building midstream and syncing to downstream 🆕
• 39 restricted dependencies used in che-code and code-rhel8 container builds #21931
• Deduplicate samples between che-samples and devspaces-samples #21586
• Enable CI builds for che-incubator/configbump, including updated secrets #21988
• The set-output command is deprecated and will be disabled by May 2023 #21993

• ⚪

• Mention, in che-incubator org, that Eclipse Che is a registered trademark of the Eclipse Foundation #21944

[nickboldt]

Prod items (ci/release labels):

• CRW-3805 create latest tags in devspaces-samples projects - Mykhailo [WIP]
• CRW-3336 migrate pluginregistry to cachito - Sam [WIP]
• P1 Enable CI builds for che-incubator/configbump, including updated secrets Enable CI builds for che-incubator/configbump, including updated secrets #21988 - Dmytro
• P1 Set buildx version to v0.9.1 in workflows that use docker/setup-buildx-action@v2 Set set provenance:false in workflows with docker/build-push-action (remove 0.9.1 pin in use docker/setup-buildx-action) #21954

Backlog/next sprint:

• P1 CRW-3581 enable github to jira integration (openshift-ci)
• P2 39 restricted dependencies used in code-rhel8 container build 39 restricted dependencies used in che-code and code-rhel8 container builds #21931
• P3 The set-output command is deprecated and will be disabled by May 2023 The set-output command is deprecated and will be disabled by May 2023 #21993

[azatsarynnyy]

Two issues to make Che-Code CI build more stable:

• Make Che-Code CI build more stable when downloading artifacts from api.github.com #22003
• Make Che-Code CI build more stable when downloading artifacts from artifacts.electronjs.org/headers #22004

[l0rd]

unplanned new issue https://issues.redhat.com/browse/CRW-4043

[azatsarynnyy]

added one more unplanned issue https://issues.redhat.com/browse/CRW-4053

[musienko-maxim]

can we add the issues?:
https://issues.redhat.com/browse/CRW-3893
https://issues.redhat.com/browse/CRW-3936

[azatsarynnyy]

added an unplanned issue: CRW-3942

[azatsarynnyy]

one more added #22024

[RomanNikitenko]

I think we should add this blocker issue to the sprint https://issues.redhat.com/browse/CRW-4089

[l0rd]

I think we should add this blocker issue to the sprint issues.redhat.com/browse/CRW-4089

I have changed the priority of that issue to critical for now as it doesn't look like a blocker.

[azatsarynnyy]

added #22037

[l0rd]

Sprint completed