---
title: "Customizing a default Code Studio pipeline"
date: "2024-02-14T06:18:38+00:00"
summary: "Learn how to customize Code Studio pipelines, modify jobs, build front-end dependencies, and change Node.js versions for your projects."
image:
type: "page"
url: "/acquia-cloud-platform/add-ons/code-studio/customizing-default-code-studio-pipeline"
id: "e2344686-8bc1-4455-9f1f-f782e5c3a191"
---

Note

*   For information about the default `.gitlab-ci.yml` file used in the Code Studio pipeline, see the [standard template](https://code.acquia.com/acquia/standard-template/-/blob/master/gitlab-ci/Auto-DevOps.acquia.gitlab-ci.yml?ref_type=heads).
*   The code examples in this section can be used for Node.js applications by including `acquia/node-template` instead of `acquia/standard-template`:
    
        include:
        - project: 'acquia/node-template'
    

Table of contents will be added

Using a custom `.gitlab-ci.yml` file
------------------------------------

To use a custom `.gitlab-ci.yml` file to customize a default Code Studio pipeline, change the CI/CD configuration file path of the project:

1.  Click **Settings** > **CI/CD**.
2.  In the General pipelines section, click **Expand** and then enter the path to the custom `.gitlab-ci.yml` file.
3.  Click **Save changes**.

Note

To revert to the original configuration file settings, set the path to `gitlab-ci/Auto-DevOps.acquia.gitlab-ci.yml@acquia/standard-template`.

Customizing jobs
----------------

For any default job run by Code Studio Auto DevOps, you can:

*   [Enable or disable the job using an environment variable](/acquia-cloud-platform/add-ons/code-studio/docs/customizing-code-studio/default-code-studio-pipeline/environment-variables?previewMode=revision#section-using-environment-variables-to-enable-or-disable-a-cicd-job).
*   [Add custom scripts to Code Studio jobs](/acquia-cloud-platform/add-ons/code-studio/adding-custom-scripts-code-studio-jobs "Adding custom scripts to Code Studio jobs").
    ========================================================================================================================================================================
    
*   Replace the default script with your own custom script.

Building front-end dependencies
-------------------------------

A common use case for customizing a job is to build front-end dependencies. Front-end dependencies include final front-end asset files, such as minified `.css` and `.js` files. You can build front-end dependencies it in many ways. A quick way to build front-end dependencies is to add [post-install-cmd](https://getcomposer.org/doc/articles/scripts.md#command-events) to your project’s `composer.json` file. The `post-install-cmd` must contain the commands that must be executed to build your front-end dependencies.

For example, in `composer.json`:

    "post-install-cmd": [
     "cd docroot/themes/custom/<my_theme> && rm -rf node_modules && npm install && npm run build"
    ]                                        

Ensure that you add the path to your custom theme in the `installer-paths` key of the `composer.json` file. For an example, see [drupal-recommended-project](https://github.com/acquia/drupal-recommended-project/blob/master/composer.json#L91).

Changing the Node.js version
----------------------------

For information about changing the Node.js version of your Drupal or Node.js application, visit [Changing the Node.js version](/acquia-cloud-platform/add-ons/code-studio/changing-nodejs-version "Changing the Node.js version").