[Timebox] Workflows

[Devessier]

I will work two days in this sprint. My main objective is to define a roadmap as clear as possible to let @thomtrp continue the work.

I should document:

• How to launch the workflow worker
• The packages that I migrated from activepieces to Twenty
• The services that remain to be integrated (like the internal API Activepieces uses to communicate between the worker and the main backend process)
• The parts that we can cut and should mock for now (like activepieces' code executor)

[greptile-apps[bot]]

To address the issue of timeboxing workflows, you can add a timeout-minutes field to each job in the workflow YAML files. Here are the steps:

1. CI Chrome Extension (.github/workflows/ci-chrome-extension.yaml):

   jobs:
    chrome-extension-build:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

2. CI Front (.github/workflows/ci-front.yaml):

   jobs:
    front-sb-build:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...
    front-sb-test:
      runs-on: ci-8-cores
      timeout-minutes: 30
      ...
    front-sb-test-performance:
      runs-on: ci-8-cores
      timeout-minutes: 30
      ...
    front-chromatic-deployment:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...
    front-task:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

3. CI Server (.github/workflows/ci-server.yaml):

   jobs:
    server-test:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

4. CI Website (.github/workflows/ci-website.yaml):

   jobs:
    website-build:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

5. CI Utils (.github/workflows/ci-utils.yaml):

   jobs:
    danger-js:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...
    congratulate:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

6. CD Deploy Main (.github/workflows/cd-deploy-main.yaml):

   jobs:
    deploy-main:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

7. CD Deploy Tag (.github/workflows/cd-deploy-tag.yaml):

   jobs:
    deploy-tag:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

8. CI Release Create (.github/workflows/ci-release-create.yaml):

   jobs:
    create_pr:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

9. CI Release Merge (.github/workflows/ci-release-merge.yaml):

   jobs:
    tag_and_release:
      runs-on: ubuntu-latest
      timeout-minutes: 30
      ...

10. CI Test Docker Compose (.github/workflows/ci-test-docker-compose.yaml):

    jobs:
      test:
        runs-on: ubuntu-latest
        timeout-minutes: 30
        ...

References

/.github/workflows/cd-deploy-main.yaml /.github/workflows/cd-deploy-tag.yaml /.github/workflows/ci-chrome-extension.yaml /.github/workflows/ci-front.yaml /.github/workflows/ci-release-create.yaml /.github/workflows/ci-release-merge.yaml /.github/workflows/ci-server.yaml /.github/workflows/ci-test-docker-compose.yaml /.github/workflows/ci-utils.yaml /.github/workflows/ci-website.yaml

#### About Greptile

This response provides a starting point for your research, not a precise solution. Help us improve! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. [Ask Greptile](https://app.greptile.com/chat/github/twentyhq/twenty/main) · [Edit Issue Bot Settings](https://app.greptile.com/apps/github)