Acquia Copilot is a conversational AI connected into our product documentation and knowledge base. Ask Copilot about product features, technical details, troubleshooting and how to get started with Acquia products.
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.
Commit composer.lock.
Use Composer 2.
Analyze the delta between a working composer.lock and the failing composer.lock.
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.
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.
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.
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:
Remove the rector.php file at the root of your project.
Run cp vendor/palantirnet/drupal-rector/rector.php to recopy the rector.php file to your project.
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.
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.
[email protected]: 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:
Navigate to your Code Studio project.
Click Clone.
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.
To update your git remote:
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
Add the new remote using the copied HTTPS URL.
If you want your remote name to be origin, run the following:
Found errors in your .gitlab-ci.yml: '<job2>' job needs '<job1>' job, but '<job1>' 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.
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/<USERNAME>/<PROJECT-NAME>.git/'
The build branch '<BRANCH_NAME>' 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.
The source branch exists on a fork instead of the main repository.
Solution
To create the branch artifact:
Add the ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT environment variable to your project.
Set the value of ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT to true.
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.
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
FAQs
How do I enable Code Studio for my Acquia subscription?
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:
Update your template to remove the SAST and secret detection report files.
Verify no untracked files remain in the job environment.
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:
Go to the project settings at <project-path>/-/settings/ci_cd#js-token-access.
In Job token permission, locate CI/CD job token allowlist and add the required group or projects to the allowlist.
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:
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.
If a merge request cannot be declined/merged immediately for some reason, one way is to stop the CDE environment:
Log in to Code Studio.
Navigate to Environments.
Determine the respective environment with the same feature branch name, and stop the environment.
Wait for a few minutes for the current pipeline to succeed, and to delete the existing CDE with the same name.
Make some minor changes to the current feature’s merge request to re-initiate the pipeline with the CDE creation job.
Resolution 2:
Rename the existing CD environment that is pointing to the same source branch from Acquia Cloud.
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.
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.
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.
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:
In the left navigation pane, click Settings > CI/CD.
Expand the Auto DevOps section.
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.
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:
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.
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.
Commit composer.lock.
Use Composer 2.
Analyze the delta between a working composer.lock and the failing composer.lock.
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.
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.
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.
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:
Remove the rector.php file at the root of your project.
Run cp vendor/palantirnet/drupal-rector/rector.php to recopy the rector.php file to your project.
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.
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.
[email protected]: 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:
Navigate to your Code Studio project.
Click Clone.
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.
To update your git remote:
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
Add the new remote using the copied HTTPS URL.
If you want your remote name to be origin, run the following:
Found errors in your .gitlab-ci.yml: '<job2>' job needs '<job1>' job, but '<job1>' 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.
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/<USERNAME>/<PROJECT-NAME>.git/'
The build branch '<BRANCH_NAME>' 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.
The source branch exists on a fork instead of the main repository.
Solution
To create the branch artifact:
Add the ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT environment variable to your project.
Set the value of ACQUIA_JOBS_CREATE_BRANCH_ARTIFACT to true.
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.
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
FAQs
How do I enable Code Studio for my Acquia subscription?
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:
Update your template to remove the SAST and secret detection report files.
Verify no untracked files remain in the job environment.
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:
Go to the project settings at <project-path>/-/settings/ci_cd#js-token-access.
In Job token permission, locate CI/CD job token allowlist and add the required group or projects to the allowlist.
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:
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.
If a merge request cannot be declined/merged immediately for some reason, one way is to stop the CDE environment:
Log in to Code Studio.
Navigate to Environments.
Determine the respective environment with the same feature branch name, and stop the environment.
Wait for a few minutes for the current pipeline to succeed, and to delete the existing CDE with the same name.
Make some minor changes to the current feature’s merge request to re-initiate the pipeline with the CDE creation job.
Resolution 2:
Rename the existing CD environment that is pointing to the same source branch from Acquia Cloud.
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.
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.
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.
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:
In the left navigation pane, click Settings > CI/CD.
Expand the Auto DevOps section.
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.
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:
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.
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.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
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.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Code Studio