About codestudio
codestudio is a skill for setting up Acquia Code Studio projects on ACE subscriptions. It guides project configuration and PHP build-version changes, but directs build execution and log operations to pipelines-cli.
Key features
- 01Guided Code Studio project setup
- 02GitLab project connection
- 03CI/CD variable configuration
- 04PHP build-version changes
- 05Migration guidance for pipeline configuration
Use cases
- 01Onboard an application to Code Studio
- 02Update the PHP version used in builds
- 03Migrate from acquia-pipelines.yml to .gitlab-ci.yml
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ acquia/ acquia-skills --skill codestudioAfter installing, type/codestudioin Claude Code to confirm it loaded.
Details
From the project READMECode Studio with Acquia CLI
Platform: This skill applies to ACE (Acquia Cloud Enterprise) subscriptions only.
Use when:
- Setting up a new Code Studio project for a Cloud application
- Changing the PHP version used in Code Studio builds
- Migrating an existing
acquia-pipelines.ymlto a.gitlab-ci.ymlfile
Note: This skill covers Code Studio setup only. To trigger builds, check job status, or stream logs, use pipelines-cli (
pipelines-cli-pipeline-operations).
Code Studio is Acquia's GitLab-based CI/CD platform. It runs build pipelines, automated tests, and deployments for your Cloud Platform applications.
Set Up Code Studio (Wizard)
The wizard creates and configures a Code Studio project for your application:
acli codestudio:wizard
Alias: acli cs:wizard
The wizard will:
- Authenticate with your Cloud Platform application
- Connect to your GitLab instance
- Create or configure a Code Studio project
- Set up CI/CD variables
Non-interactive (provide all credentials upfront):
acli codestudio:wizard \
--key="$ACQUIA_KEY" \
--secret="$ACQUIA_SECRET" \
--gitlab-token="$GITLAB_TOKEN" \
--gitlab-project-id=12345 \
--gitlab-host-name=code.acquia.com
Security: Never pass credential values directly in the command line — they appear in shell history and process listings. Always source them from environment variables or a secrets manager.
Options:
| Option | Description |
|---|---|
--key | Cloud Platform API key for Code Studio to use |
--secret | Cloud Platform API secret for Code Studio to use |
--gitlab-token | GitLab personal access token |
--gitlab-project-id | Integer project ID of the GitLab project to configure |
--gitlab-host-name | GitLab hostname (defaults to Acquia's instance) |
Change PHP Version in Code Studio
Update the PHP version used in Code Studio build containers:
acli codestudio:php-version <version>
Example:
acli codestudio:php-version 8.2
acli codestudio:php-version 8.3
Typical Workflow: Onboard to Code Studio
# Step 1: Set up Code Studio project
acli codestudio:wizard
# Step 2: Set PHP version if needed
acli codestudio:php-version 8.2
Best Practices
- Run the wizard first — It sets up all required CI/CD variables automatically.
- Use environment variables for credentials in CI — Pass
--key,--secret, and--gitlab-tokenvia environment variables (e.g.,--key="$ACQUIA_KEY"), never as literal values. Store secrets in your CI/CD platform's secret store. - Match PHP versions — Ensure
codestudio:php-versionmatches the version in yourcomposer.jsonplatform requirements.
Troubleshooting
"GitLab project not found"
Verify the project ID and that your token has access:
# Re-run wizard interactively to select the right project
acli codestudio:wizard
Authentication errors
Ensure your Cloud API key/secret are valid:
acli auth:login
acli auth:me
Related Topics
- Getting Started — Authentication setup
- Environment Management — Deploy to environments
- Pull & Push — Push build artifacts