[JetBrains] Upgrade IDEs to 2025.1

[mustard-mh]

Description

Related Issue(s)

Fixes CLC-1310

How to test

Integration test

https://github.com/gitpod-io/gitpod/actions/runs/14601192805/job/40960860418?pr=20763

Smoke test

• Start workspace with stable JetBrains IDEs (like IntelliJ and WebStorm)
• It can connect with Gateway
• Previous JetBrains IDEs are pin-able (you could check previous version on gitpod.io)

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - hw-jb-stable
• 🔗 URL - hw-jb-stable.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - hw-jb-stable-gha.32222
• 🗒️ Logs - GCP Logs Explorer

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=jetbrains
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[mustard-mh]

v2 has some issues [gha], upgrade to v4 helps, see [gha]

[mustard-mh]

Smoke test

IntelliJ IDEA	GoLand

Editor versions

Img

[mustard-mh]

@iQQBot could you have a look? 🙏

[iQQBot]

smoke test works

[lwoerdeman]

Hi @mustard-mh - it looks like the Intellij 2025.1 update failed to push due to a terraform issue.

https://github.com/gitpod-io/gitpod/actions/runs/14634884998/job/41063988951

Maybe it shouldn't have the trailing - in pd-update-team-, which looks like it's coming from previewctl get name?

[mustard-mh]

Hi @lwoerdeman , 2025.1 has released on production environment (https://gitpod.io)

gitpod.io

In case you want to know more details: here's the GitHub Action which triggered production release https://github.com/gitpod-io/gitpod/actions/runs/14611289425/job/40991977651

What most matters is the Build Gitpod step, as it build components into images, and then the install-app (production) step which will trigger the release flow