Skip to content

Conversation

@tsahil01
Copy link

@tsahil01 tsahil01 commented Nov 6, 2025

ref #1064

  • Speed up Playwright E2E test workflow by disabling unused Supabase services and enabling Docker layer caching.
  • reduces the time of e2e setup and using cache it is again further reduced for next commits in the same PR

Changes

1. Disabled unused supabase services

  • Disabled realtime service as e2e tests don't test real-time subscriptions
  • Disabled storage service as e2e tests don't test S3 persistence
  • Saves time by skipping 2 Docker image pulls

2. Enabled Docker BuildKit caching

  • Added docker/setup-buildx-action@v3
  • Enabled DOCKER_BUILDKIT=1
  • Caches Docker image layers between workflow runs
  • Saves times on subsequent commits by reusing cached layers

Use of AI

  • none

Copy link
Author

@tsahil01 tsahil01 left a comment

Choose a reason for hiding this comment

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

added self review comments.
@slavingia can you approve the workflow for this? Thanks.

Comment on lines +26 to +27
DOCKER_BUILDKIT: 1
BUILDKIT_PROGRESS: plain
Copy link
Author

Choose a reason for hiding this comment

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

  • allows Docker to cache image layers between runs
  • show plain progress output cleaner github actions logs


[realtime]
enabled = true
enabled = false
Copy link
Author

Choose a reason for hiding this comment

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

  • disable realtime service: not used by E2E tests as tests only validate http responses and not live subscriptions


[storage]
enabled = true
enabled = false
Copy link
Author

Choose a reason for hiding this comment

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

  • disable storage service: not used by E2E tests as tests check UI, not S3 file persistence

@stefanbinoj
Copy link
Contributor

added self review comments. @slavingia can you approve the workflow for this? Thanks.

@tsahil01, I think you could trigger CI by clicking the Update Branch button.

Also, it would be great if you could remove the fix # from the PR description, as it might automatically close the issue if this PR gets merged. It’s better to change it to ref # or part of # (or something similar) instead.

@tsahil01
Copy link
Author

tsahil01 commented Nov 6, 2025

added self review comments. @slavingia can you approve the workflow for this? Thanks.

@tsahil01, I think you could trigger CI by clicking the Update Branch button.

Also, it would be great if you could remove the fix # from the PR description, as it might automatically close the issue if this PR gets merged. It’s better to change it to ref # or part of # (or something similar) instead.

I think Sahil needs to approve this so that I can run the CI:
Screenshot 2025-11-06 at 6 20 41 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants