Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Explain role of Pipelines #863

Merged
merged 1 commit into from
Dec 27, 2016
Merged

Explain role of Pipelines #863

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion readme/deploy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ This document outlines the workflow to build a complete Drupal docroot (plus sup

The most important thing to remember about this workflow is that the Github and Acquia Cloud repos are _not_ clones of one another. Github only stores the source code, and Acquia Cloud only stores the production code (i.e. the build artifacts).

Currently, this workflow can either be followed manually, or integrated into a CI solution such as Jenkins or Travis. Eventually, Build Steps will enable it to run directly on Acquia Cloud, obviating the need to maintain separate repositories for source code (Github) and production code (Acquia Cloud).
Currently, this workflow can either be followed manually, or integrated into a CI solution such as Jenkins or Travis. Acquia Pipelines enables your build to run directly on the Acquia platform, integrating the separate repositories for development workflow (Github) and production code (Acquia Cloud).

## First time setup

Expand Down