Skip to content

chore: configure Amp orb lifecycle - #24723

Closed
connoro13c wants to merge 2 commits into
twentyhq:mainfrom
connoro13c:chore/amp-orb-setup
Closed

chore: configure Amp orb lifecycle#24723
connoro13c wants to merge 2 commits into
twentyhq:mainfrom
connoro13c:chore/amp-orb-setup

Conversation

@connoro13c

@connoro13c connoro13c commented Aug 24, 2026

Copy link
Copy Markdown

Summary

  • add idempotent orb setup for pinned Node.js/Yarn, JavaScript dependencies, Playwright Chromium, PostgreSQL 16, Redis, environment files, and the built twenty-shared package
  • add a fast resume hook that repairs PostgreSQL and Redis after orb wake
  • ignore generated Amp portal metadata

Verification

  • ran .agents/setup twice: 63s cold and 51s warm
  • stopped PostgreSQL and Redis, then verified .agents/resume repaired both in 2.75s
  • verified Node 24.16.0 and Yarn 4.13.0 from a clean non-interactive login shell
  • ran the full Nx test target inventory; all unit targets passed, including the flaky SDK target on retry
  • ran twenty-zapier:test against a seeded server: 25 tests passed
  • ran twenty-e2e-testing:test against the CI-style app: 9 tests passed

Review in cubic

ampagent and others added 2 commits August 24, 2026 21:31
@twenty-ci-bot-public

Copy link
Copy Markdown

👋 Thanks for contributing to Twenty! We're excited to have you on board.

Your PR has been set to draft while you work on it. Once you're done, mark it as Ready for review and our automated checks will run.

By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement.

@github-actions

Copy link
Copy Markdown
Contributor

Welcome!

Hello there, congrats on your first PR! We're excited to have you contributing to this project.
By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement.

Generated by 🚫 dangerJS against 007394e

@greptile-apps

greptile-apps Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR adds lifecycle scripts for preparing and resuming an Amp orb development environment.

  • Installs pinned Node.js and Yarn versions, system services, JavaScript dependencies, and Playwright Chromium.
  • Configures and starts PostgreSQL 16 and Redis, provisions development databases and environment files, and builds twenty-shared.
  • Ignores generated Amp portal metadata.

Confidence Score: 5/5

The PR appears safe to merge with no concrete changed-code failure identified for the intended Amp orb environment.

The setup and resume scripts consistently provision and reference PostgreSQL 16, Redis, the repository-pinned Node and Yarn versions, required databases, environment examples, and the shared-package build.

Important Files Changed

Filename Overview
.agents/setup Adds an idempotent environment bootstrap covering toolchains, dependencies, local services, databases, environment files, and shared-package output.
.agents/resume Adds a lightweight wake hook that repairs and verifies the PostgreSQL and Redis services installed by setup.
.gitignore Excludes generated Amp portal metadata from version control.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  Setup[.agents/setup] --> Node[Install pinned Node.js and Yarn]
  Setup --> Packages[Install PostgreSQL 16 and Redis]
  Setup --> Dependencies[Install JavaScript and Playwright dependencies]
  Setup --> Shared[Build twenty-shared]
  Setup --> Prepare[Prepare databases and environment files]
  Prepare --> Resume[.agents/resume]
  Resume --> PostgreSQL[Ensure PostgreSQL is ready]
  Resume --> Redis[Ensure Redis is ready]
Loading

Reviews (1): Last reviewed commit: "chore: complete Amp orb test setup" | Re-trigger Greptile

@connoro13c connoro13c closed this Aug 24, 2026
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.

2 participants