--- title: "FAQs and troubleshooting" date: "2024-02-14T06:18:38+00:00" summary: "Find answers to common questions about Drupal errors, Code Studio features, and integrations. Troubleshoot issues with pipelines, authentication, and customization options for your development workflow." image: type: "page" url: "/acquia-cloud-platform/add-ons/code-studio/faqs-and-troubleshooting" id: "7b80d06e-6ca8-46bd-8b16-6d92ca33148e" --- Table of contents will be added Common error messages related to Drupal --------------------------------------- ### [Composer memory limit error - Build Code](#id48) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Build Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-build-drupal-stage) [Build Code](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-build-code-job) `Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/bin/composer/src/ Composer/DependencyResolver/Solver.php on line 201.` Application Customer **Potential cause** The application uses an older version of the Drupal Starter Kits project template, which causes a Composer memory limit error. **Solution** Confirm that your application meets the following best practices: * From `composer.json`, remove the lines that point to the old Drupal Starter Kits project template. Drupal Starter Kits utilizes the [Acquia Drupal recommended project](https://github.com/acquia/drupal-recommended-project#acquia-drupal-recommended-project). * Commit `composer.lock`. * Use Composer 2. * Analyze the delta between a working `composer.lock` and the failing `composer.lock`. * * * ### [Missing Test Drupal job error](#id50) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `'Create artifact from branch' job needs 'Test Drupal' job, but 'Test Drupal' is not in any previous stage.` Application Customer **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](/acquia-cloud-platform/add-ons/code-studio/customizing/default-code-studio-pipeline) back in the `before_script` and `after_script` parameters. * * * ### [$rector\_bin process error](#id52) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Automatic Updates](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-automatic-updates-stage) [Deprecated Code Update](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deprecated-code-update-job) `Command [$rector_bin process ${ACQUIA_CUSTOM_CODE_DIRS} --ansi] exited with code [1]` Application Customer **Potential cause** The existing Drupal code is deprecated. **Solution** Identify the files with deprecated Drupal code and update the code. * * * ### [PHPStan error](#id53) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [PHP Stan](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `Command ["$CI_PROJECT_DIR"/vendor/bin/phpstan] exited with code [1]` Application Customer **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](#id56) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Build Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-build-drupal-stage) [Build Code](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-build-code-job) `Your lock file does not contain a compatible set of packages. Please run composer update.` `symfony/string vx.x.x requires php >=8.2 -> your php version (8.1) does not satisfy that requirement.` Application Customer **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](/acquia-cloud-platform/add-ons/code-studio/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-modifying-environment-variables). Note Setting the `PHP_VERSION` variable in the `.gitlab-ci.yml` file might not work as expected. Acquia recommends that you set variable values through the Code Studio UI. The `composer.json` file in your project, [Cloud IDE](/acquia-cloud-platform/add-ons/ide), [Code Studio](/acquia-cloud-platform/add-ons/code-studio/overview "Overview"), and [Cloud Platform](/acquia-cloud-platform/overview "Overview") must use the same PHP version. * * * ### [PHPUnit error](#id60) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `Class "Behat\Mink\Element\TraversableElement" not found` Application Customer **Potential cause** Certain packages are missing from your project. **Solution** If your application runs on the [current Drupal version](/service-offerings/guide/software-life-cycle#supported-drupal-version), add the `core-dev` package to your project: composer require --dev drupal/core-dev * * * ### [Yarn not found error](#id63) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `Yarn not found` Application Customer **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](#id61) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `Error: Failed opening required '/var/www/site-php//-settings.inc'` Application Customer **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: if (file_exists('/var/www/site-php')) { require('/var/www/site-php//-settings.inc'); } 2. Update the `if` statement to specify the complete path to the file: if (file_exists('/var/www/site-php//-settings.inc')) { * * * ### [Scheduled job rector errors](#id83) **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. **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `Undefined constant Rector\Core\Configuration\Option::IMPORT_DOC_BLOCKS` Application Customer **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** **Build stage** **Job** **Error message** **Category** **Responsibility** [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-stage) [Test Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-test-drupal-job) `Symfony\Component\DependencyInjection\Loader\Configurator\ContainerConfigurator::__construct(): Argument #1 ($container) must be of type Symfony\Component\DependencyInjection\ContainerBuilder, RectorPrefix202208\Symfony\Component\DependencyInjection\ContainerBuilder given, called in /home/codestudio/.config/composer/vendor/rector/rector/vendor/symfony/dependency-injection/Loader/PhpFileLoader.php on line 67` Application Customer 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](#common-error-messages-drupal-nodejs) ------------------------------------------------------------------------------------------- ### [Code push error](#id49) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Deploy Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deploy-drupal-stage) [Deploy Branch to Acquia and Deploy Tag to Acquia jobs](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deploy-branch-to-acquia-and-deploy-tag-to-acquia-jobs) `In PushArtifactCommand.php line 100: [Acquia\Cli\Exception\AcquiaCliException] Pushing code was aborted because your local Git repository has uncommitted changes. Please either commit, reset, or stash your changes via git.` Application Customer **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](https://github.com/acquia/drupal-recommended-project/blob/master/.gitignore). 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. Note The system does not remove the files from your local machine during the commit process. The system removes the files from other developers' machines when they run `git pull`. **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Deploy Drupal](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deploy-drupal-stage) Build artifact from branch/tag `Permission denied (publickey).` `fatal: Could not read from remote repository.` `Please make sure you have the correct access rights and the repository exists.` Platform Customer **Potential causes** * The user is not a member of the Cloud Platform subscription. * The user's [role](/acquia-cloud-platform/working-roles-and-permissions "https://docs.acquia.com/acquia-cloud-platform/access/teams/roles") in Cloud Platform does not have access to push code. * Cloud Platform has an issue. **Solutions** * Confirm that the user is a [member](/acquia-cloud-platform/managing-team-members "https://docs.acquia.com/acquia-cloud-platform/access/teams/members") of the Cloud Platform subscription. * Confirm that the user's [role](/acquia-cloud-platform/working-roles-and-permissions "https://docs.acquia.com/acquia-cloud-platform/access/teams/roles") in Cloud Platform has access to push code. For more information, see [Managing users, teams, roles, and permissions](/acquia-cloud-platform/managing-users-teams-roles-and-permissions "https://docs.acquia.com/acquia-cloud-platform/access/teams"). * Verify that Cloud Platform does not have an issue. For more information, see [Acquia, Inc. Status](http://status.acquia.com/). **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** N/A N/A `git@gitcode.acquia.com: Permission denied (publickey,keyboard-interactive). fatal: Could not read from remote repository.` `Please make sure you have the correct access rights and the repository exists.` N/A Customer **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. ![The Clone button is at the top-right and the Copy icon is next to the Clone with HTTPS field.](https://acquia.widen.net/content/6jfjvxuxzi/jpeg/code-studio_clone-with-https.jpeg?position=c&color=ffffffff&quality=80&u=0b06mk) 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: 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: git remote add origin * * * ### Missing [job error - gitlab-ci.yml](#id51) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** All N/A `Found errors in your .gitlab-ci.yml: '' job needs '' job, but '' is not in any previous stage.` Application Customer **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](#id55) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Deploy](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deploy-drupal-stage) Creating Artifact `glab auth git-credential: "erase" is an invalid operation remote: HTTP Basic: Access denied. The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. See https://code.acquia.com/help/topics/git/troubleshooting_git #error-on-git-fetch-http-basic-access-denied fatal: Authentication failed for 'https://code.acquia.com//.git/'` Application Customer **Potential cause** Your token has expired. **Solution** Use `glab auth login` to configure the token again. * * * ### [Missing build branch error](#id57) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** [Deploy](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-deploy-drupal-stage) Create Acquia CDE `The build branch '' is missing from Acquia Cloud Platform` Application Customer **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](/acquia-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](/acquia-cloud-platform/add-ons/code-studio/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-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](#id58) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** Varies Varies `ERROR: Uploading artifacts. 413 Request Entity Too Large.` Platform Customer **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](/service-offerings/tam) or [Acquia Support](/service-offerings/support#contact-acquia-support) to increase the maximum artifact size. * * * ### [Missing token error](#id59) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** Varies Varies `Error writing data to auth/jwt/login: Error making API request. Code: 400. Errors: * missing token` Application Customer 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](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/drupal-auto-devops/autodevops-jobs#section-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](#id62) **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** N/A N/A `Pipeline cannot be run. You do not have sufficient permission to run a pipeline on 'main'. Please select a different branch or contact your administrator for assistance.` Application Customer **Potential cause** Only owners and maintainers have access to run a pipeline on the `main` branch. **Solution** Contact your administrator. * * * ### Login error **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** N/A N/A `Your account is pending approval from an Acquia administrator. If it has been more than 24 hours, please contact Acquia Support.` Application Customer **Potential cause** The user does not have a Code Studio seat. **Solution** [Assign a Code Studio seat to the user](/acquia-cloud-platform/add-ons/code-studio/assigning-and-revoking-user-seats "Assigning and revoking user seats"). * * * ### Project setup - 401 Unauthorized error **Description** **Build stage** **Job** **Error message** **Category** **Responsibility** N/A N/A `401 Unauthorized` Application Customer **Potential cause** If you see an unauthorized error during `acli cs:wizard --gitlab-host-name=code.acquia.com`, it is likely that you do not have the required role in Code Studio. **Solution** Ensure that a user with the role **Owner** or **Maintainer** role in Code Studio runs the project setup. For information about roles and permissions, visit [User roles and permissions](/acquia-cloud-platform/add-ons/code-studio/assigning-and-revoking-user-seats "https://docs.acquia.com/acquia-cloud-platform/add-ons/code-studio/getting-started/managing-user-seats#section-user-roles-and-permissions"). * * * ### HTTP Basic: Access denied  **Build Stage** **Job** **Error Message** **Category** **Responsibility** **Automatic Updates** Composer Update `remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password.` Application Customer **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](#generate-new-token). 2. [Update the corresponding variable in your CI/CD settings](#update-pat-variable). 3. [Trigger a new pipeline run](#run-automatic-update-pipeline). #### Generating a new project access token 1. Log in to the [Code Studio user interface](http://code.acquia.com/). 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. ![acquia-dam_create-token](https://acquia.widen.net/content/523898db-ef93-47b2-9649-ef2f1540099c/web/fccb1_create%20token.png?w=720&itok=jJYLCzho) 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**. ![acquia-dam_ci-cd-variables](https://acquia.widen.net/content/636a6c0f-b586-48cf-b480-acb8447a9bf0/web/cd8fc_edit%20variable.png?w=480&itok=aGbCOR3l) #### 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. ![acquia-dam_pipeline](https://acquia.widen.net/content/b1492454-aa48-4827-9400-a8b3eaa61c9e/web/eedc6_new%20pipeline.png?w=480&itok=qOoGVJ6y) Important If you generate a new token, you must run a new pipeline using the instructions. Clicking the re-run pipeline button on a previous failed pipeline run does not use the new token and continues to fail. * * * ### 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](/acquia-cloud-platform/add-ons/code-studio/getting-started/enabling-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](/service-offerings/support#contact-acquia-support). ### What versions of Drupal does Code Studio support? Code Studio supports the [current Drupal version](/service-offerings/guide/software-life-cycle#supported-drupal-version). ### What versions of Node.js does Code Studio support? Code Studio supports Node.js versions 20 and 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](https://docs.gitlab.com/user/permissions/#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 `/-/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](https://github.com/acquia/drupal-recommended-project/blob/master/.gitignore). ### How do I install private packages through Composer? Composer provides [multiple mechanisms for downloading private packages](https://getcomposer.org/doc/articles/authentication-for-private-packages.md). Acquia recommends that you store authentication credentials in a project `auth.json`. For more information, see [Authentication in auth.json per project](https://getcomposer.org/doc/articles/authentication-for-private-packages.md#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](/service-offerings/support#contact-acquia-support). ### 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](/acquia-cloud-platform#cloud-next-cloud-classic). 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](/acquia-cloud-platform/add-ons/code-studio/getting-started/setting-up-project). For more information, see the following tutorials on [dev.acquia.com](https://dev.acquia.com/): * [Setting up a new project in Code Studio using a Cloud IDE](https://dev.acquia.com/tutorial/how-set-new-project-code-studio-using-cloud-ide) * [Connecting Cloud IDE to Code Studio](https://dev.acquia.com/tutorial/connecting-cloud-ide-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](/service-offerings/guide/software-life-cycle#supported-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](/acquia-cloud-platform/add-ons/code-studio/customizing/repository-mirroring). ### 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](/acquia-cloud-platform/add-ons/code-studio/customizing/default-code-studio-pipeline/advanced-tutorials/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](/acquia-cloud-platform/add-ons/code-studio/adding-custom-scripts-code-studio-jobs "Adding custom scripts to Code Studio jobs"). For more information about implementing Veracode Static analysis as part of the pipeline, see [GitLab Pipeline Scan Examples](https://docs.veracode.com/r/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](#id79) 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](/acquia-cloud-platform/add-ons/code-studio/customizing/default-code-studio-pipeline). ### [What is a build minute in Code Studio?](#id91) 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. Note Disabling Auto DevOps removes the Acquia-optimized steps needed to build, test, and deploy Drupal applications to Acquia Cloud. 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](/service-offerings/guide/product-support-scope/code-studio). ### 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](/service-offerings/support#contact-acquia-support). ### [Can Code Studio integrate with SonarCube?](#id92) Yes, Code Studio can integrate with SonarCube. For more information, see SonarCube's documentation on [Gitlab integration](https://docs.sonarsource.com/sonarqube-server/10.5/devops-platform-integration/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 `/`, and the default output directory is `/.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](/acquia-cloud-platform/add-ons/code-studio/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-adding-environment-variables). To disable certain tasks in the Test stage, see [Environment variables to enable or disable a CI/CD job](/acquia-cloud-platform/add-ons/code-studio/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-using-environment-variables-to-enable-or-disable-a-cicd-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](/acquia-cloud-platform/add-ons/code-studio/customizing-code-studio/default-code-studio-pipeline/environment-variables#section-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](/acquia-cloud-platform/add-ons/code-studio/adding-custom-scripts-code-studio-jobs "Adding custom scripts to Code Studio jobs") 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](/acquia-cloud-platform/add-ons/code-studio/drupal-auto-devops "Drupal Auto DevOps") replaced BLT commands with [Acquia CLI commands](/acquia-cloud-platform/add-ons/acquia-cli/commands "Acquia CLI Commands") as of March 3, 2025. Acquia recommends that you [remove BLT](https://dev.acquia.com/tutorial/you-dont-need-blt-acquia-cloud) from your project.