Skip to content

Conversation

@akosyakov
Copy link
Member

Description

Automation is reusing the same branch and same preview envs correspondingly. On harvester there are various issues networks, like stale load balancer for long living preview envs, or network rate limitting. This PR is switching to GCE to avoid it.

Related Issue(s)

Fixes #

How to test

Release Notes

NONE

Documentation

Build Options:

  • /werft with-werft
    Run the build with werft instead of GHA
  • leeway-no-cache
  • /werft no-test
    Run Leeway with --dont-test
Publish Options
  • /werft publish-to-npm
  • /werft publish-to-jb-marketplace
Installer Options
  • with-dedicated-emulation
  • with-ws-manager-mk2
  • workspace-feature-flags
    Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

  • /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
  • with-integration-tests=all
    Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

to avoid networking issues
@roboquat roboquat merged commit d9ae6f7 into main Mar 31, 2023
@roboquat roboquat deleted the ak/jb_gce branch March 31, 2023 05:34
@roboquat roboquat added deployed: IDE IDE change is running in production deployed Change is completely running in production labels Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

deployed: IDE IDE change is running in production deployed Change is completely running in production release-note-none size/XS team: IDE

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants