vscode:go
About 358 wordsAbout 1 min
vscode:go
When to use it: use it when you want some preparation to finish before developers enter the Workspaces environment - for example installing dependencies or starting services before opening the entry point, so the environment is not still warming up when they arrive. It only affects the timing of the entry points, not whether Workspaces itself is available.
Difference in configuring this built-in task for Workspaces:
- Using this task: When starting cloud-native development, you need to wait for this task to complete before the WebIDE and VS Code / Cursor client entry points appear.
- Not using this task: After the pipeline's prepare stage completes (code-server code service starts), the WebIDE and VS Code / Cursor client entry points will appear before the stages tasks are executed.
The difference in the timing of the appearance of the entry points mentioned above refers to the transition from the loading waiting page to the entry point selection page. In reality, whether or not this task is used, Workspaces is already available once the code-server code service has started.
Waiting Time
This task delays when the entry point appears.
Applicable Events
vscodebranch.createapi_triggerweb_trigger
Output Results
{
// WebIDE URL
"url": ""
}Configuration Examples
$:
# vscode event: specifically for starting Workspaces in the page
vscode:
- docker:
# Use a custom image as the development environment;
# if not provided, the default image
# cnbcool/default-dev-env:latest will be used
image: cnbcool/default-dev-env:latest
services:
- vscode
- docker
stages:
# Wait for this task to complete before entering the development environment
- name: pre-entry preparation
script: ls -al
- name: vscode go
type: vscode:go
# Tasks that can be executed after entering the development environment
- name: post-entry initialization
script: ls -al