Using Acquia Pipelines with Front End Hosting - Advanced

Using Acquia Pipelines with Front End Hosting - Advanced

Acquia Pipelines with Front End Hosting - Advanced enables you to build application artifacts for Node V3 applications and deploy the generated pipelines-build-* branch to the target environment.

Note

Acquia Pipelines on Front End Hosting - Advanced (FEHA) does not support artifact builds. Acquia Pipelines on FEHA supports only branch and tag builds.

Support and trigger behaviors depend on the connected repository source:

• GitHub repositories: Support automatic job triggers after repository connection. When you push branches or commits that contain acquia-pipelines.yaml, Pipelines jobs are triggered.

• Bitbucket repositories: Follow the same behavior as GitHub repositories. Pushes to branches with acquia-pipelines.yaml trigger Pipelines jobs after connection.

• Acquia Git repositories: Do not support automatic job triggers. You must start jobs manually.

Important

When you use Acquia Git as the source repository, Pipelines does not trigger jobs for commits in Cloud Next. To run a build, you must start the job manually in the Cloud Platform UI.  

Prerequisites

• Application type: Your application type must be Front End Hosting - Advanced.

• Repository availability: Your code repository must be available in GitHub, Bitbucket, or Acquia Git.

• File requirement: Your code branch must include an acquia-pipelines.yaml file.

• Framework configuration: Configure the code branch according to the framework documentation.

• Automatic triggers: To start build jobs automatically after commit jobs, use GitHub or Bitbucket.

Repository connection options

For repository connection setup and management details, visit Managing your repository connection.

Repository source	Supported with Acquia Pipelines on Node V3?	Automatic pipelines job build trigger?	Notes
GitHub

Note

Update the nvm use command to match the Node.js version that your application supports. For Node V3 workloads, use Node.js 22 or Node.js 24 as appropriate for your application.

Acquia Pipelines documentation references

• Starting a pipeline job: To select a branch and start a job from the Acquia Cloud Platform UI, visit Starting a pipeline job.

• Reviewing job output: To open job details and review command output for troubleshooting, visit Viewing job output.

• Reviewing job history: To check the job status and history for an application, visit Viewing Pipelines job history.

Best practice

Use GitHub or Bitbucket for an automated build workflow. Use Acquia Git if manual build starts are acceptable for your team.

Yes

Configuring Pipelines for Node V3

To configure Pipelines for Node V3:

1. Log in to Acquia Cloud Platform.

2. Select your application.

3. In the left navigation menu, click Pipelines.

4. Click Settings.

5. Under Connected repository, select the repository type to use: Acquia Git, GitHub, or Bitbucket.

   • For details on GitHub repository connections, visit Connecting Pipelines to your GitHub repoConnecting Pipelines to your GitHub repository.

   • For details on Bitbucket repository connections, visit Connecting Pipelines to your Bitbucket repoConnecting Pipelines to your Bitbucket repository.

6. Complete the repository configuration. For details, visit Managing your repository connection.

7. Configure the code branch according to the framework documentation in Getting startedSetting up Node.js applications.

8. Add or update the acquia-pipelines.yaml file in the code branch of the connected repository.

9. Commit changes to the repository branch that Acquia Pipelines builds. Webhooks start Pipelines jobs for new commits or pull requests based on the connected repository configuration.

10. Start a pipeline job manually. For details, visit Starting a pipeline jobStarting a pipeline job.

    Note

    If an Acquia Pipelines job runs for a branch that does not contain an acquia-pipelines.yaml file, the Acquia Pipelines job adds an example acquia-pipelines.yaml file to the repository and creates a pipelines-build-* branch. Do not deploy that generated branch to any environment until you review and replace the example file with a valid build definition for your application.

Handling sensitive values in Acquia Pipelines

Acquia Pipelines build jobs must use sensitive information, such as SSH keys, access tokens, or passwords, to access private resources during the code build. Do not add these values in plain text to acquia-pipelines.yaml. Encrypt the sensitive value and reference it in a secure element in the build definition file.

For the encryption workflow and command syntax, visit Encrypting keys and variables and Managing your Pipelines from the command line.

Example acquia-pipelines.yaml for Node V3

Build output and deployment

After successful pipeline completion, Pipelines creates a build artifact branch named pipelines-build-[BRANCHNAME]. To deploy the output:

1. Navigate to Environments.
2. Locate the destination environment card.
3. Use the Code action on the card to switch code to the generated pipelines-build-* branch.

Prerequisites

• Application type: Your application type must be Front End Hosting - Advanced.

• Repository availability: Your code repository must be available in GitHub, Bitbucket, or Acquia Git.

• File requirement: Your code branch must include an acquia-pipelines.yaml file.

• Framework configuration: Configure the code branch according to the framework documentation.

• Automatic triggers: To start build jobs automatically after commit jobs, use GitHub or Bitbucket.

Repository connection options

For repository connection setup and management details, visit Managing your repository connection.

For details on GitHub repository connections, visit Connecting Pipelines to your GitHub repoConnecting Pipelines to your GitHub repository.