FAQs and troubleshooting

FAQs and troubleshooting

composer require --dev drupal/core-dev                                                                  

Solution

You can use yarn by adding the following lines in the .gitlab-ci.yml file:

Error in opening a required file

Description

Solution

You must update the if statement in the Cloud Platform database settings as follows:

1. In the settings.php file of your project, locate a statement similar to the erroneous statement. For example:

   copy

   if (file_exists('/var/www/site-php')) {
       require('/var/www/site-php/<APP>/<APP>-settings.inc');                                                                                                                                               }

2. Update the if statement to specify the complete path to the file:

   copy

   if (file_exists('/var/www/site-php/<APP>/<APP>-settings.inc')) { 

Scheduled job rector errors

Description

This error is usually a result of an older version of rector being added in your project. Code Studio attempts to add the latest version of rector during the Pipeline. However, it uses your version if that is included in your project’s composer.lock file.

Resolution 1:

1. Run composer remove palantirnet/drupal-rector.
2. Delete the rector.php file from the root of your project, allowing Code Studio to handle the rector going forward.

Resolution 2:

1. Run composer update palantirnet/drupal-rector -W to upgrade your rector package to the latest rector version.
2. Remove the rector.php file from the root of your project.
3. Run cp vendor/palantirnet/drupal-rector/rector.php to recopy the rector.php file.

Description

This error indicates that your project’s rector.php file needs to be recreated. Newer versions of rector altered the configuration syntax, resulting in your rector.php file no longer being valid.

Resolution:

1. Remove the rector.php file at the root of your project.
2. Run cp vendor/palantirnet/drupal-rector/rector.php to recopy the rector.php file to your project.

Common error messages related to Drupal and Node.js

Code push error

Description

Potential cause

Directories are committed in the codebase. Git must ignore the directories so that Composer can add them during the build.

Solution

Update the .gitignore file in the root directory of your project so that Git ignores the proper directories. The recommended .gitignore file is located in this location.

If Git does not ignore the pushed or tracked files even after updating the .gitignore file, run the following commands from the root directory of your project:

• git rm -r --cached .

• git add .

After executing the commands, the system displays all the files that are ignored by the current .gitignore file in staged changes.

Solutions

• Confirm that the user is a member of the Cloud Platform subscription.

• Confirm that the user's role in Cloud Platform has access to push code.

  For more information, see Managing users, teams, roles, and permissions.

• Verify that Cloud Platform does not have an issue.

  For more information, see Acquia, Inc. Status.

Description

Potential cause

If you cannot push code from your Cloud IDE or local development environment to your Code Studio repository due to this error, you must update your git remote to use the HTTPS URL instead of the SSH URL.

Solution

Update your git remote to use the HTTPS URL of your repository.

To find the HTTPS URL:

1. Navigate to your Code Studio project.
2. Click Clone.

3. Click the Copy icon to copy the value specified in the Clone with HTTPS field.

   

To update your git remote:

1. Remove the current git remote from your Cloud IDE or local development environment.

   If your remote name is origin, run the following:

   copy

   git remote remove origin                                                                                                                                               

2. Add the new remote using the copied HTTPS URL.

   If you want your remote name to be origin, run the following:

   copy

   git remote add origin <URL>                                                                                                                                               

Missing job error - gitlab-ci.yml

Description

Potential cause

One job requires another job to complete the stage, but the required dependent job is currently not running. This can occur from a number of situations, such as the job not being defined in the template or mismatching conditions for when jobs are scheduled to run.

Solution

The following are the ways to resolve this error:

• Revert to default Auto DevOps job.
• Test your .gitlab-ci.yml in CI Lint.

Access denied error

Description

Potential cause

Your token has expired.

Solution

Use glab auth login to configure the token again.

Missing build branch error

Description

Potential cause

This error occurs during merge requests if one of the following is true:

• The ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT environment variable is not set to true. The branch artifact must be created so that it can be pushed to Cloud Platform.
• The source branch exists on a fork instead of the main repository.

Solution

• To create the branch artifact:
  1. Add the ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT environment variable to your project.

  2. Set the value of ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT to true.

     For more information, see Adding environment variables.

• If the source branch does not exist in the main repository:
  1. Push the source branch to the main Code Studio project repository.
  2. Create the merge request without using a forked repository.

• Before you create a merge request using the target branch:

  1. Ensure that the target branch successfully passes a Code Studio pipeline.
  2. Deploy the target branch to Cloud Platform.

Error in uploading artifacts

Description

Potential cause

If you customize your pipeline to implement artifact-producing jobs, and your artifacts are larger than 100 MB, you might see this error. Common custom jobs that result in large artifacts are front-end tests, such as Nightwatch.js or BackstopJS.

Solution

Contact your Technical Account Manager or Acquia Support to increase the maximum artifact size.

Missing token error

Description

Potential cause

This error occurs if you customize your pipeline to use the CI_JOB_JWT variable or a similar token. The CI_JOB_JWT variable is deprecated in GitLab.

Solution

If you use the CI_JOB_JWT variable, then remove it. Add the following script to the stage or the job that you customized:

For example, if a custom job in the Test Drupal stage is Build artifact and deploy to CI Server, you must update the .gitlab-ci.yml file as follows:

Insufficient permission error

Description

Potential cause

Only owners and maintainers have access to run a pipeline on the main branch.

Solution

Contact your administrator.

Login error

Description

Potential cause

The user does not have a Code Studio seat.

Solution

HTTP Basic: Access denied 

Potential cause

The most common cause is that the project access token used for Git authentication has expired and needs to be regenerated. All access tokens expire after 12 months.

Solution

To resolve this issue, complete the following tasks:

1. Generate a new project access token.
2. Update the corresponding variable in your CI/CD settings.
3. Trigger a new pipeline run.

Generating a new project access token

1. Log in to the Code Studio user interface.
2. Navigate to the respective Code Studio project.
3. In the left sidebar, go to Settings > Access tokens.
4. Click Add new token.
5. In the Token name field, type acquia-codestudio.

6. In the Expiration date field, click the X button to clear the date.

   Clearing the date means that the token does not have an expiration.

7. In the Select a role field, select Maintainer.

8. In the Select scopes section, select the api and write_repository checkboxes.

   

9. Click Create project access token.

   Code Studio generates the token. 

10. Copy the token secret and save it to a secure location as you need to use in the next task.

Update the project access token variable

1. In the left sidebar, go to Settings > CI/CD.
2. Expand the Variables section.
3. In the row for ACQUIA_GLAB_TOKEN_SECRET, click the pencil icon to edit the variable.
4. In the Value field, add the token secret that you copied earlier.

5. Click Save changes.

   

Running the automatic updates pipeline

1. In the left sidebar, go to Build > Pipeline schedules.

2. In the row for Code Studio Automatic Updates, click the play icon to run the scheduled pipeline.

   

Code Studio supports Node.js versions 22.

What is the default MySQL version for new projects?

For new projects, the pipeline uses MySQL 8.0 as the default version unless the customer specifies a different version.

What is the default MySQL version for existing projects?

For existing projects, the pipeline uses MySQL 5.7 as the default version unless the customer specifies a different version.

How can I set a specific MySQL version for a project?

Set the required MySQL version by defining the MYSQL_VERSION variable under the Code Studio CI/CD variables for the project.

What happens on successful execution of my pipeline with MySQL 8.0 on Code Studio?

On successful execution of your pipeline with MySQL 8.0 on Code Studio, Code Studio starts deploying the changes to Acquia Cloud.

Can CodeStudio create CDEs for Codebase?

No, CodeStudio does not support the creation of CDE for Codebase.

Does the Install Drupal section in Test Job work with "sync" option?

No, the Install Drupal section in Test Job will not work with the "sync" option.

Will updating the Codebase label change the CodeStudio Project title?

No, updates to the Codebase label are not reflected on the CodeStudio Project title.

Why do Create artifact jobs fail after the GitLab v18.1.0 upgrade in Code Studio?

The GitLab v18.1.0 upgrade adds two untracked files, gl-sast-report.json and gl-secret-detection-report.json . These files can cause Create artifact jobs to fail, especially in the Deploy Drupal stage.

• If you use Acquia's standard or node template, no action is needed.

• If you use a custom template, update it to remove these files during the job.

Solution
To resolve this issue:

1. Update your template to remove the SAST and secret detection report files.

2. Verify no untracked files remain in the job environment.

3. Test your pipeline to confirm job success.

Some Code Studio users do not see all expected Code Studio features, such as triggering a pipeline when they push a branch. What could be the issue?

This issue may occur if the user does not accept the invitation email from Code Studio after seat assignment, or if their assigned role does not have the required permissions. Ask the user to check their email and accept the invitation, and review their assigned role. For more information, see Project members permissions.

Why does the CI/CD job token authentication error occur when I run a pipeline?

When you run a pipeline, authentication by CI/CD job token may not occur if the workflow project exists in another private group that does not grant access. In this case, the system displays the following error:

Solution
To resolve this issue:

1. Go to the project settings at <project-path>/-/settings/ci_cd#js-token-access.
2. In Job token permission, locate CI/CD job token allowlist and add the required group or projects to the allowlist.
3. Trigger a new pipeline.

Why am I seeing a lot of SAST jobs in my Pipeline?

Acquia recommends that you do not commit contributed dependencies to your repository. Example code for Drupal projects:

Add these to your .gitignore. For an example, see acquia/drupal-recommended-project.

How do I install private packages through Composer?

Composer provides multiple mechanisms for downloading private packages. Acquia recommends that you store authentication credentials in a project auth.json. For more information, see Authentication in auth.json per project.

This works in Code Studio CI/CD jobs.

I cannot sudo and add packages, move binaries, etc. Why?

This is a security restriction on application containers running in the Acquia Kubernetes service.

• If you’re downloading a binary, such as composer.phar or acli.phar (which Acquia has already done for you), you can place it in '$HOME/bin'. The bin folder in the CI user’s home directory is already added to $PATH. It works as long as your binary has an execute permissions set.
• To download a package through `apt` or similar, create a Support ticket.

CDE already exists. What can I do?

Error message:

Resolution 1:

If a merge request cannot be declined/merged immediately for some reason, one way is to stop the CDE environment:

1. Log in to Code Studio.
2. Navigate to Environments.
3. Determine the respective environment with the same feature branch name, and stop the environment.
4. Wait for a few minutes for the current pipeline to succeed, and to delete the existing CDE with the same name.
5. Make some minor changes to the current feature’s merge request to re-initiate the pipeline with the CDE creation job.

Resolution 2:

1. Rename the existing CD environment that is pointing to the same source branch from Acquia Cloud.
2. Make some minor changes to the current feature’s merge request to re-initiate the pipeline with CDE creation job.

Is there a limit to the number of projects I can have in Code Studio?

No. You can have unlimited projects in Code Studio. However, the Code Studio Auto DevOps pipeline requires your Code Studio project to be linked to an Acquia Cloud application. You can link only one Code Studio project to a given Cloud application.

Does Code Studio work with Cloud IDE?

Yes. For instructions on how to set up Code Studio with Cloud IDE, see Setting up a Code Studio project.

For more information, see the following tutorials on dev.acquia.com:

• Setting up a new project in Code Studio using a Cloud IDE
• Connecting Cloud IDE to Code Studio

Can I restore a project marked as pending for deletion?

You cannot restore a project marked as pending for deletion. Attempting to restore such a project may create data inconsistencies or cause unexpected issues. The system completes the deletion process within one day.

Can I use an existing application with Code Studio?

Yes. Code Studio is compatible with existing applications running Drupal Starter Kits, and the current Drupal version or the current Node.js version.

Can I use a third-party repository with Code Studio?

Yes. You can use a third-party repository with Code Studio. For instructions on how to integrate your private repository with Code Studio, see Configuring repository mirroring in Code Studio.

Does Code Studio work with Jira?

You can integrate Code Studio with Jira Issues and Jira Development Panel. For more information about setting up the integration, see Integrating Code Studio with Jira.

Can you integrate a Veracode Static analysis with the Code Studio Auto DevOps pipeline

Yes. You can integrate a Veracode Static analysis by customizing the standard template for the Drupal Auto DevOps pipeline or by customizing the node template for the Node.js Auto DevOps pipeline.

To customize the Auto DevOps pipeline in Code Studio, see Adding a before_script or after_script to a Code Studio job.

For more information about implementing Veracode Static analysis as part of the pipeline, see GitLab Pipeline Scan Examples.

How many users can I add to Code Studio?

With Code Studio entitlements, seats are equivalent to users. The number of seats within your Code Studio subscription is equal to the number of users you can add to your Code Studio instance.

For more questions about Code Studio entitlements, contact your Acquia account team.

Why can I not manage certain seats in Code Studio?

If you assign seats through the Code Studio user interface, you might encounter an error while managing such seats. Acquia recommends that you assign seats through the Cloud Platform user interface.

Can I use Code Studio with non-Drupal applications?

Code Studio is compatible with Drupal and Node.js applications.

Can I use Code Studio with a Node.js application?

Yes. Code Studio is compatible with Drupal or Node.js applications.

Can I customize Code Studio builds?

Yes. You can customize Code Studio builds. For instructions, see Customizing a default Code Studio pipeline.

What is a build minute in Code Studio?

A build minute is one minute of execution time of a single Code Studio job. Build minutes are the sum of the durations of every job that you execute using Code Studio, including the jobs that run concurrently. For example, if you ran five jobs with each job using ten build minutes, then you used fifty build minutes.

Is there a limit to the build minutes for Code Studio?

Yes. Build time is limited to 10k minutes per group per year. 

Can I use my own container image in a Code Studio job?

No. With the Auto DevOps pipeline, Acquia maintains the container images used in Code Studio jobs. You can customize jobs, but the base images are selected by Acquia as secure, vetted options that remove overhead for our users.

Can I disable Auto DevOps?

Yes, you can disable Auto DevOps.

To disable Auto DevOps:

1. In the left navigation pane, click Settings > CI/CD.
2. Expand the Auto DevOps section.
3. Clear the Default to Auto DevOps pipeline checkbox.

Does Code Studio work with Acquia Site Factory?

Yes. The continuous integration (CI) feature of Code Studio is compatible with Acquia Site Factory. However, the continuous delivery (CD) feature of Code Studio is not compatible with Acquia Site Factory.

For more information, see the Code Studio product support scope.

Can I use my own GitLab license with Code Studio?

No. External licenses for Gitlab cannot be used with Acquia Code Studio.

How do I enable or execute PHPUnit tests in the Test Drupal stage?

Ensure that the ACQUIA_TASKS_PHPUNIT and ACQUIA_TASKS_SETUP_DRUPAL environment variables are set to true.

Do Code Studio runners use specific IP addresses that I can allowlist?

Yes. To obtain a list of IP addresses, contact Acquia Support.

Can Code Studio integrate with SonarCube?

Yes, Code Studio can integrate with SonarCube. For more information, see SonarCube's documentation on Gitlab integration.

How do I enable code coverage in PHPUnit?

Code Studio does not support PHPUnit code coverage.

How do I specify the root directory or output directory for my Node.js project?

• To specify the root directory, add the directory path to the extra.acquia.root_directory section in the package.json file of the root directory.
• To specify the output directory, add the directory path to the extra.acquia.output_directory section in the package.json file of the root directory. For example:

The default root directory is <project_root>/, and the default output directory is <project_root>/.next/.

Can I turn off the Test stage or Deploy stage in my Node.js Auto DevOps pipeline?

Yes, you can turn off these stages in your Node.js Auto DevOps pipeline:

• To turn off the Test stage, add the NODE_JOBS_TEST environment variable in Code Studio and set it to false. This setting also disables all jobs in the Test stage. For more information, see Adding environment variables. To disable certain tasks in the Test stage, see Environment variables to enable or disable a CI/CD job.
• To turn off the Deploy stage, add the NODE_JOBS_DEPLOY environment variable in Code Studio and set it to false. This setting also disables all jobs in the Deploy stage. For more information, see Adding environment variables.

Which package managers does Code Studio support for Node.js Auto DevOps?

Node Package Manager (NPM) is the only supported package manager in Code Studio. However, you can choose to use a before_script or after_script to modify the default pipeline and install packages using yarn.

Why are certain files in my Node.js Auto DevOps pipeline being excluded from the build artifact?

Code Studio excludes files with the following naming patterns as they are not required for build artifacts:

• .hg
• .git
• .gitmodules
• .svn
• .cache
• .eslintrc
• .now
• .vercel
• .npmignore
• .dockerignore
• .gitignore
• .*.swp
• .DS_Store
• .wafpicke-*
• .lock-wscript
• .env.local
• .env.*.local
• .venv
• npm-debug.log
• config.gypi
• node_modules
• __pycache__
• venv
• CVS

If a mandatory file is missing from a build artifact, rename the file to ensure that the name does not contain any of the preceding naming patterns.

Does Code Studio support BLT?

The Auto DevOps pipeline replaced BLT commands with Acquia CLI commands as of March 3, 2025. Acquia recommends that you remove BLT from your project.

Missing Test Drupal job error

Description

Potential cause

The Acquia Auto DevOps template is copied incorrectly in the entire codebase.

Solution

Remove everything in the file and add any necessary customization back in the before_script and after_script parameters.

$rector_bin process error

Description

Potential cause

The existing Drupal code is deprecated.

Solution

Identify the files with deprecated Drupal code and update the code.

PHPStan error

Description

Potential cause

The existing code does not follow the proper coding standards.

Solution

Identify the files with code standards errors and update the code.

PHP version error - Build Code

Description

Potential cause

The PHP version of the project is not set correctly.

Solution

Add the PHP_VERSION environment variable to your project through the UI, and set its value to the PHP version that your project uses. This value accepts major and minor versions only, for example, 8.2. For more information, see Modifying environment variables.

PHPUnit error

Description

Potential cause

Certain packages are missing from your project.

Solution

If your application runs on the current Drupal version, add the core-dev package to your project:

composer require --dev drupal/core-dev                                                                  

Yarn not found error

Description

Solution

You can use yarn by adding the following lines in the .gitlab-ci.yml file:

Test Drupal:
  before_script:
    - eval $YARN_PACKAGE
    - eval $YARN_PATH

Error in opening a required file

Description

Solution

You must update the if statement in the Cloud Platform database settings as follows:

1. In the settings.php file of your project, locate a statement similar to the erroneous statement. For example:

   copy

   if (file_exists('/var/www/site-php')) {
       require('/var/www/site-php/<APP>/<APP>-settings.inc');                                                                                                                                               }

2. Update the if statement to specify the complete path to the file:

   copy

   if (file_exists('/var/www/site-php/<APP>/<APP>-settings.inc')) { 

Scheduled job rector errors

Description

This error is usually a result of an older version of rector being added in your project. Code Studio attempts to add the latest version of rector during the Pipeline. However, it uses your version if that is included in your project’s composer.lock file.

Resolution 1:

1. Run composer remove palantirnet/drupal-rector.
2. Delete the rector.php file from the root of your project, allowing Code Studio to handle the rector going forward.

Resolution 2:

1. Run composer update palantirnet/drupal-rector -W to upgrade your rector package to the latest rector version.
2. Remove the rector.php file from the root of your project.
3. Run cp vendor/palantirnet/drupal-rector/rector.php to recopy the rector.php file.

Description

This error indicates that your project’s rector.php file needs to be recreated. Newer versions of rector altered the configuration syntax, resulting in your rector.php file no longer being valid.

Resolution:

1. Remove the rector.php file at the root of your project.
2. Run cp vendor/palantirnet/drupal-rector/rector.php to recopy the rector.php file to your project.

Common error messages related to Drupal and Node.js

Code push error

Description

Potential cause

Directories are committed in the codebase. Git must ignore the directories so that Composer can add them during the build.

Solution

Update the .gitignore file in the root directory of your project so that Git ignores the proper directories. The recommended .gitignore file is located in this location.

If Git does not ignore the pushed or tracked files even after updating the .gitignore file, run the following commands from the root directory of your project:

• git rm -r --cached .

• git add .

After executing the commands, the system displays all the files that are ignored by the current .gitignore file in staged changes.

Description

Potential causes

• The user is not a member of the Cloud Platform subscription (glossary term, activate to view definition).

• The user's role in Cloud Platform does not have access to push code.

• Cloud Platform has an issue.

Solutions

• Confirm that the user is a member of the Cloud Platform subscription.

• Confirm that the user's role in Cloud Platform has access to push code.

  For more information, see Managing users, teams, roles, and permissions.

• Verify that Cloud Platform does not have an issue.

  For more information, see Acquia, Inc. Status.

Description

Potential cause

If you cannot push code from your Cloud IDE or local development environment to your Code Studio repository due to this error, you must update your git remote to use the HTTPS URL instead of the SSH URL.

Solution

Update your git remote to use the HTTPS URL of your repository.

To find the HTTPS URL:

1. Navigate to your Code Studio project.
2. Click Clone.

3. Click the Copy icon to copy the value specified in the Clone with HTTPS field.

   

To update your git remote:

1. Remove the current git remote from your Cloud IDE or local development environment.

   If your remote name is origin, run the following:

   copy

   git remote remove origin                                                                                                                                               

2. Add the new remote using the copied HTTPS URL.

   If you want your remote name to be origin, run the following:

   copy

   git remote add origin <URL>                                                                                                                                               

Missing job error - gitlab-ci.yml

Description

Potential cause

One job requires another job to complete the stage, but the required dependent job is currently not running. This can occur from a number of situations, such as the job not being defined in the template or mismatching conditions for when jobs are scheduled to run.

Solution

The following are the ways to resolve this error:

• Revert to default Auto DevOps job.
• Test your .gitlab-ci.yml in CI Lint.

Access denied error

Description

Potential cause

Your token has expired.

Solution

Use glab auth login to configure the token again.

Missing build branch error

Description

Potential cause

This error occurs during merge requests if one of the following is true:

• The ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT environment variable is not set to true. The branch artifact must be created so that it can be pushed to Cloud Platform.
• The source branch exists on a fork instead of the main repository.

Solution

• To create the branch artifact:
  1. Add the ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT environment variable to your project.

  2. Set the value of ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT to true.

     For more information, see Adding environment variables.

• If the source branch does not exist in the main repository:
  1. Push the source branch to the main Code Studio project repository.
  2. Create the merge request without using a forked repository.

• Before you create a merge request using the target branch:

  1. Ensure that the target branch successfully passes a Code Studio pipeline.
  2. Deploy the target branch to Cloud Platform.

Error in uploading artifacts

Description

Potential cause

If you customize your pipeline to implement artifact-producing jobs, and your artifacts are larger than 100 MB, you might see this error. Common custom jobs that result in large artifacts are front-end tests, such as Nightwatch.js or BackstopJS.

Solution

Contact your Technical Account Manager or Acquia Support to increase the maximum artifact size.

Missing token error

Description

Potential cause

This error occurs if you customize your pipeline to use the CI_JOB_JWT variable or a similar token. The CI_JOB_JWT variable is deprecated in GitLab.

Solution

If you use the CI_JOB_JWT variable, then remove it. Add the following script to the stage or the job that you customized:

id_tokens:
  VAULT_ID_TOKEN:
    aud: $VAULT_ADDR                                                                                  

For example, if a custom job in the Test Drupal stage is Build artifact and deploy to CI Server, you must update the .gitlab-ci.yml file as follows:

"Build artifact and deploy to CI Server":
  stage: "Build Drupal"
  id_tokens:
    VAULT_ID_TOKEN:
      aud: $VAULT_ADDR

Insufficient permission error

Description

Potential cause

Only owners and maintainers have access to run a pipeline on the main branch.

Solution

Contact your administrator.

Login error

Description

Potential cause

The user does not have a Code Studio seat.

Solution

HTTP Basic: Access denied 

Potential cause

The most common cause is that the project access token used for Git authentication has expired and needs to be regenerated. All access tokens expire after 12 months.

Solution

To resolve this issue, complete the following tasks:

1. Generate a new project access token.
2. Update the corresponding variable in your CI/CD settings.
3. Trigger a new pipeline run.

Generating a new project access token

1. Log in to the Code Studio user interface.
2. Navigate to the respective Code Studio project.
3. In the left sidebar, go to Settings > Access tokens.
4. Click Add new token.
5. In the Token name field, type acquia-codestudio.

6. In the Expiration date field, click the X button to clear the date.

   Clearing the date means that the token does not have an expiration.

7. In the Select a role field, select Maintainer.

8. In the Select scopes section, select the api and write_repository checkboxes.

   

9. Click Create project access token.

   Code Studio generates the token. 

10. Copy the token secret and save it to a secure location as you need to use in the next task.

Update the project access token variable

1. In the left sidebar, go to Settings > CI/CD.
2. Expand the Variables section.
3. In the row for ACQUIA_GLAB_TOKEN_SECRET, click the pencil icon to edit the variable.
4. In the Value field, add the token secret that you copied earlier.

5. Click Save changes.

   

Running the automatic updates pipeline

1. In the left sidebar, go to Build > Pipeline schedules.

2. In the row for Code Studio Automatic Updates, click the play icon to run the scheduled pipeline.

   

FAQs

How do I enable Code Studio for my Acquia subscription?

For information about enabling Code Studio for your subscription, see Enabling a Code Studio subscription.

Can the owner of a subscription enable Code Studio?

Yes, the owner of a subscription can enable Code Studio.

Can I disable Code Studio from the Cloud Platform user interface?

No, you cannot disable Code Studio from the Cloud Platform user interface. To disable your Code Studio subscription, contact Acquia Support.

What versions of Drupal does Code Studio support?

Code Studio supports the current Drupal version.

What versions of Node.js does Code Studio support?

Code Studio supports Node.js versions 22.

What is the default MySQL version for new projects?

For new projects, the pipeline uses MySQL 8.0 as the default version unless the customer specifies a different version.

What is the default MySQL version for existing projects?

For existing projects, the pipeline uses MySQL 5.7 as the default version unless the customer specifies a different version.

How can I set a specific MySQL version for a project?

Set the required MySQL version by defining the MYSQL_VERSION variable under the Code Studio CI/CD variables for the project.

What happens on successful execution of my pipeline with MySQL 8.0 on Code Studio?

On successful execution of your pipeline with MySQL 8.0 on Code Studio, Code Studio starts deploying the changes to Acquia Cloud.

Can CodeStudio create CDEs for Codebase?

No, CodeStudio does not support the creation of CDE for Codebase.

Does the Install Drupal section in Test Job work with "sync" option?

No, the Install Drupal section in Test Job will not work with the "sync" option.

Will updating the Codebase label change the CodeStudio Project title?

No, updates to the Codebase label are not reflected on the CodeStudio Project title.

Why do Create artifact jobs fail after the GitLab v18.1.0 upgrade in Code Studio?

The GitLab v18.1.0 upgrade adds two untracked files, gl-sast-report.json and gl-secret-detection-report.json . These files can cause Create artifact jobs to fail, especially in the Deploy Drupal stage.

• If you use Acquia's standard or node template, no action is needed.

• If you use a custom template, update it to remove these files during the job.

Solution
To resolve this issue:

1. Update your template to remove the SAST and secret detection report files.

2. Verify no untracked files remain in the job environment.

3. Test your pipeline to confirm job success.

Some Code Studio users do not see all expected Code Studio features, such as triggering a pipeline when they push a branch. What could be the issue?

This issue may occur if the user does not accept the invitation email from Code Studio after seat assignment, or if their assigned role does not have the required permissions. Ask the user to check their email and accept the invitation, and review their assigned role. For more information, see Project members permissions.

Why does the CI/CD job token authentication error occur when I run a pipeline?

When you run a pipeline, authentication by CI/CD job token may not occur if the workflow project exists in another private group that does not grant access. In this case, the system displays the following error:

Cloning into '/workflow'...
remote: Authentication by CI/CD job token not allowed.
fatal: unable to access 'https://code.acquia.io/workflow/': The requested URL returned error: 403

Solution
To resolve this issue:

1. Go to the project settings at <project-path>/-/settings/ci_cd#js-token-access.
2. In Job token permission, locate CI/CD job token allowlist and add the required group or projects to the allowlist.
3. Trigger a new pipeline.

Why am I seeing a lot of SAST jobs in my Pipeline?

Acquia recommends that you do not commit contributed dependencies to your repository. Example code for Drupal projects:

git rm -r --cached vendor docroot/core docroot/libraries docroot/modules/contrib docroot/themes/contrib docroot/profiles/contrib node_modules

Add these to your .gitignore. For an example, see acquia/drupal-recommended-project.

How do I install private packages through Composer?

Composer provides multiple mechanisms for downloading private packages. Acquia recommends that you store authentication credentials in a project auth.json. For more information, see Authentication in auth.json per project.

This works in Code Studio CI/CD jobs.

I cannot sudo and add packages, move binaries, etc. Why?

This is a security restriction on application containers running in the Acquia Kubernetes service.

• If you’re downloading a binary, such as composer.phar or acli.phar (which Acquia has already done for you), you can place it in '$HOME/bin'. The bin folder in the CI user’s home directory is already added to $PATH. It works as long as your binary has an execute permissions set.
• To download a package through `apt` or similar, create a Support ticket.

CDE already exists. What can I do?

Error message:

CDE environment with name CDE-xxxx already exists                                                                                

Resolution 1:

If a merge request cannot be declined/merged immediately for some reason, one way is to stop the CDE environment:

1. Log in to Code Studio.
2. Navigate to Environments.
3. Determine the respective environment with the same feature branch name, and stop the environment.
4. Wait for a few minutes for the current pipeline to succeed, and to delete the existing CDE with the same name.
5. Make some minor changes to the current feature’s merge request to re-initiate the pipeline with the CDE creation job.

Resolution 2:

1. Rename the existing CD environment that is pointing to the same source branch from Acquia Cloud.
2. Make some minor changes to the current feature’s merge request to re-initiate the pipeline with CDE creation job.

Is there a limit to the number of projects I can have in Code Studio?

No. You can have unlimited projects in Code Studio. However, the Code Studio Auto DevOps pipeline requires your Code Studio project to be linked to an Acquia Cloud application. You can link only one Code Studio project to a given Cloud application.

Does Code Studio work with Cloud IDE?

Yes. For instructions on how to set up Code Studio with Cloud IDE, see Setting up a Code Studio project.

For more information, see the following tutorials on dev.acquia.com:

• Setting up a new project in Code Studio using a Cloud IDE
• Connecting Cloud IDE to Code Studio

Can I restore a project marked as pending for deletion?

You cannot restore a project marked as pending for deletion. Attempting to restore such a project may create data inconsistencies or cause unexpected issues. The system completes the deletion process within one day.

Can I use an existing application with Code Studio?

Yes. Code Studio is compatible with existing applications running Drupal Starter Kits, and the current Drupal version or the current Node.js version.

Can I use a third-party repository with Code Studio?

Yes. You can use a third-party repository with Code Studio. For instructions on how to integrate your private repository with Code Studio, see Configuring repository mirroring in Code Studio.

Does Code Studio work with Jira?

You can integrate Code Studio with Jira Issues and Jira Development Panel. For more information about setting up the integration, see Integrating Code Studio with Jira.

Can you integrate a Veracode Static analysis with the Code Studio Auto DevOps pipeline

Yes. You can integrate a Veracode Static analysis by customizing the standard template for the Drupal Auto DevOps pipeline or by customizing the node template for the Node.js Auto DevOps pipeline.

To customize the Auto DevOps pipeline in Code Studio, see Adding a before_script or after_script to a Code Studio job.

For more information about implementing Veracode Static analysis as part of the pipeline, see GitLab Pipeline Scan Examples.

How many users can I add to Code Studio?

With Code Studio entitlements, seats are equivalent to users. The number of seats within your Code Studio subscription is equal to the number of users you can add to your Code Studio instance.

For more questions about Code Studio entitlements, contact your Acquia account team.

Why can I not manage certain seats in Code Studio?

If you assign seats through the Code Studio user interface, you might encounter an error while managing such seats. Acquia recommends that you assign seats through the Cloud Platform user interface.

Can I use Code Studio with non-Drupal applications?

Code Studio is compatible with Drupal and Node.js applications.

Can I use Code Studio with a Node.js application?

Yes. Code Studio is compatible with Drupal or Node.js applications.

Can I customize Code Studio builds?

Yes. You can customize Code Studio builds. For instructions, see Customizing a default Code Studio pipeline.

What is a build minute in Code Studio?

A build minute is one minute of execution time of a single Code Studio job. Build minutes are the sum of the durations of every job that you execute using Code Studio, including the jobs that run concurrently. For example, if you ran five jobs with each job using ten build minutes, then you used fifty build minutes.

Is there a limit to the build minutes for Code Studio?

Yes. Build time is limited to 10k minutes per group per year. 

Can I use my own container image in a Code Studio job?

No. With the Auto DevOps pipeline, Acquia maintains the container images used in Code Studio jobs. You can customize jobs, but the base images are selected by Acquia as secure, vetted options that remove overhead for our users.

Can I disable Auto DevOps?

Yes, you can disable Auto DevOps.

To disable Auto DevOps:

1. In the left navigation pane, click Settings > CI/CD.
2. Expand the Auto DevOps section.
3. Clear the Default to Auto DevOps pipeline checkbox.

Does Code Studio work with Acquia Site Factory?

Yes. The continuous integration (CI) feature of Code Studio is compatible with Acquia Site Factory. However, the continuous delivery (CD) feature of Code Studio is not compatible with Acquia Site Factory.

For more information, see the Code Studio product support scope.

Can I use my own GitLab license with Code Studio?

No. External licenses for Gitlab cannot be used with Acquia Code Studio.

How do I enable or execute PHPUnit tests in the Test Drupal stage?

Ensure that the ACQUIA_TASKS_PHPUNIT and ACQUIA_TASKS_SETUP_DRUPAL environment variables are set to true.

Do Code Studio runners use specific IP addresses that I can allowlist?

Yes. To obtain a list of IP addresses, contact Acquia Support.

Can Code Studio integrate with SonarCube?

Yes, Code Studio can integrate with SonarCube. For more information, see SonarCube's documentation on Gitlab integration.

How do I enable code coverage in PHPUnit?

Code Studio does not support PHPUnit code coverage.

How do I specify the root directory or output directory for my Node.js project?

• To specify the root directory, add the directory path to the extra.acquia.root_directory section in the package.json file of the root directory.
• To specify the output directory, add the directory path to the extra.acquia.output_directory section in the package.json file of the root directory. For example:

"extra": {       
             "acquia": {
               "root_directory": "front-end/",
               "output_directory": "assets/"
             }
            }

The default root directory is <project_root>/, and the default output directory is <project_root>/.next/.

Can I turn off the Test stage or Deploy stage in my Node.js Auto DevOps pipeline?

Yes, you can turn off these stages in your Node.js Auto DevOps pipeline:

• To turn off the Test stage, add the NODE_JOBS_TEST environment variable in Code Studio and set it to false. This setting also disables all jobs in the Test stage. For more information, see Adding environment variables. To disable certain tasks in the Test stage, see Environment variables to enable or disable a CI/CD job.
• To turn off the Deploy stage, add the NODE_JOBS_DEPLOY environment variable in Code Studio and set it to false. This setting also disables all jobs in the Deploy stage. For more information, see Adding environment variables.

Which package managers does Code Studio support for Node.js Auto DevOps?

Node Package Manager (NPM) is the only supported package manager in Code Studio. However, you can choose to use a before_script or after_script to modify the default pipeline and install packages using yarn.

Why are certain files in my Node.js Auto DevOps pipeline being excluded from the build artifact?

Code Studio excludes files with the following naming patterns as they are not required for build artifacts:

• .hg
• .git
• .gitmodules
• .svn
• .cache
• .eslintrc
• .now
• .vercel
• .npmignore
• .dockerignore
• .gitignore
• .*.swp
• .DS_Store
• .wafpicke-*
• .lock-wscript
• .env.local
• .env.*.local
• .venv
• npm-debug.log
• config.gypi
• node_modules
• __pycache__
• venv
• CVS

If a mandatory file is missing from a build artifact, rename the file to ensure that the name does not contain any of the preceding naming patterns.

Does Code Studio support BLT?

The Auto DevOps pipeline replaced BLT commands with Acquia CLI commands as of March 3, 2025. Acquia recommends that you remove BLT from your project.