Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up Bitbucket Pipeline for Acquia deployment #728

Open
mrdavidburns opened this issue Nov 1, 2024 · 1 comment
Open

Set up Bitbucket Pipeline for Acquia deployment #728

mrdavidburns opened this issue Nov 1, 2024 · 1 comment
Labels
architecture Issues that have to do with the architecture and philosophy of Drainpipe documentation Improvements or additions to documentation enhancement New feature or request lsm

Comments

@mrdavidburns
Copy link
Member

depends on: #454

Using the task commands set up in #454 let's add a composer.json Drainpipe configuration that will scaffold a Bitbucket Pipeline for deploying to Acquia. Let's have it so that this happens anytime something gets merged into main branch.

This would match functionality that we do with PantheonReviewApps

@mrdavidburns mrdavidburns added documentation Improvements or additions to documentation enhancement New feature or request architecture Issues that have to do with the architecture and philosophy of Drainpipe lsm labels Nov 1, 2024
@mrdavidburns
Copy link
Member Author

As discussed during Drainpipe sync (11/4/24) let's hold off on having Drainpipe do the scaffolding for Bitbucket Pipelines. Let's build those directly on the projects that need this functionality and once we have 3 or more clients that need this functionality we'll have working examples to reference to help standardize this into Drainpipe.

Unassigning for now and setting to Blocked for reason stated above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture Issues that have to do with the architecture and philosophy of Drainpipe documentation Improvements or additions to documentation enhancement New feature or request lsm
Projects
None yet
Development

No branches or pull requests

2 participants