Skip to content

Conversation

@geropl
Copy link
Member

@geropl geropl commented Jan 9, 2026

Description

Fix preview environment workflows that were failing due to GCP OIDC authentication issues and missing leeway command.

Fixes CLC-2190

Root causes:

  1. Docker-based actions (preview-create, deploy-gitpod, deploy-monitoring-satellite) couldn't access GCP credentials due to filesystem path mismatches and permission issues when running in isolated containers
  2. Several jobs using delete-preview (a composite action) were missing the container specification, causing leeway: command not found errors

Solution:

  • Convert Docker-based actions to composite actions, which run in the same context as the job and avoid credential access issues
  • Add container specifications to all jobs that use preview-related actions
image

Changes

Actions converted from Docker to composite:

  • .github/actions/preview-create/
  • .github/actions/deploy-gitpod/
  • .github/actions/deploy-monitoring-satellite/

Workflows updated with container specifications:

Workflow Jobs updated
build.yml infrastructure, install, monitoring
branch-build.yml infrastructure, install, monitoring
ide-integration-tests.yml infrastructure, delete
workspace-integration-tests.yml infrastructure, delete
preview-env-check-regressions.yml infrastructure, delete
preview-env-gc.yml delete

Related Issue(s)

N/A - discovered during CI analysis

How to test

  1. start workspace from this branch (I used catfood)
  2. leeway run dev:preview 🪄

The delete job was missing the container specification, causing
'leeway: command not found' errors. Use the same dev-environment
container as the stale job.

Co-authored-by: Ona <[email protected]>
Convert preview-create, deploy-gitpod, and deploy-monitoring-satellite
from Docker-based actions to composite actions. This fixes GCP OIDC
authentication failures caused by credential file permission issues
when Docker actions mount the workspace.

Docker actions run in isolated containers where the credentials file
path from the host doesn't match the container's filesystem, and file
permissions prevent access. Composite actions run in the same context
as the job, avoiding these issues.

Changes:
- Convert 3 Docker actions to composite actions
- Add container spec to infrastructure/install/monitoring jobs in:
  - build.yml
  - branch-build.yml
  - ide-integration-tests.yml
  - workspace-integration-tests.yml
  - preview-env-check-regressions.yml
- Remove unused inputs (infrastructure_provider, image_repo_base,
  previewctl_hash) from action calls

Co-authored-by: Ona <[email protected]>
Add missing container specification to delete jobs in:
- ide-integration-tests.yml
- workspace-integration-tests.yml
- preview-env-check-regressions.yml

The delete-preview action is a composite action that requires leeway,
which is only available in the dev-environment container.

Co-authored-by: Ona <[email protected]>
@geropl geropl changed the title [preview] Add container to GC delete job [preview] Fix preview environment workflows Jan 9, 2026
@geropl geropl marked this pull request as ready for review January 9, 2026 16:53
@geropl geropl requested a review from a team as a code owner January 9, 2026 16:53
npmPublishTrigger: "false"
publishToNPM: true
publishToJBMarketplace: true
npmPublishTrigger: false
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This...


leeway build \
-Dversion="${VERSION}" \
-DlocalAppVersion="${VERSION}" \
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

... and this was the crucial changes to make previews work again - not sure how it ever worked before 🙈

@geropl geropl merged commit 80317ca into main Jan 12, 2026
37 of 39 checks passed
@geropl geropl deleted the gpl/fix-previews branch January 12, 2026 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants