Auto-cancel prebuilds on outdated commits

July 4, 2022

Auto-cancel prebuilds on outdated commits

During development, sometimes a number of commits occur within a short period of time, which can trigger and queue multiple prebuilds for the same branch.

Gitpod will now auto-cancel pending or running prebuilds on the same branch when new commits are pushed, efficiently processing the queue and making sure workspaces always use prebuilds with the latest commits.

Auto-cancellation has been enabled by default for all projects, but you can disable this behavior in project settings.

Roadmap updates

JetBrains - Roadmap issue: #7956 Beta

#10986 - Ports opened by tasks defined in .gitpod.yml are now automatically forwarded in JetBrains IDEs.
#10974 - Respect user settings (proxies, certificates) of JetBrains Gateway while connecting to Gitpod API.

Fixes and improvements

#11083 - Fix the start-workspace flow for when a prebuild got auto-cancelled
#11074 - Fix prebuild permissions
#11072 - Resolve performance degradation issue by changing ws-proxy to not use the target host when serving workspace port route
#11026 - Improve reliability of log streaming for image builds and prebuilds
#10836 - Provide endpoint that allows retrieving information about the workspace from within the workspace
#10696 - Prebuild status is shown under the logs when starting a workspace.
#10962 - Automatically cancel outdated prebuilds (i.e. new commits are pushed on a branch). This behavior can be disabled in the project’s settings.
#10952 - Update docker compose to v2.6.1
#10882, #10727 - Fix prebuilds stuck in queued indefinitely