Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix worker run ci step #7437

Merged
merged 7 commits into from
Oct 4, 2024
Merged

Fix worker run ci step #7437

merged 7 commits into from
Oct 4, 2024

Conversation

Weiko
Copy link
Member

@Weiko Weiko commented Oct 4, 2024

Context

Updating the Worker / Run step to run in sync mode with in-memory cache type so it does not hang forever in the CI.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This pull request adds a timeout to the worker run step in the CI configuration for the Twenty project.

  • Modified CI configuration to include a timeout for the worker run step, likely improving CI pipeline stability
  • Specific details of the timeout duration and affected workflows are not provided in the available information
  • Changes appear to be focused on CI/CD improvements rather than application code modifications

No file(s) reviewed, no comment(s)
Edit PR Review Bot Settings

@Weiko Weiko changed the title Set timeout to worker run ci step Fix worker run ci step Oct 4, 2024
@Weiko Weiko merged commit bd305c8 into main Oct 4, 2024
4 of 5 checks passed
@Weiko Weiko deleted the c--ci-server-set-timeout-to-worker-run branch October 4, 2024 17:28
harshit078 pushed a commit to harshit078/twenty that referenced this pull request Oct 14, 2024
## Context
Updating the Worker / Run step to run in sync mode with in-memory cache
type so it does not hang forever in the CI.
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