Currently an Enterprise Dapp takes two pipelines at all times: One to deploy Source to GitHub, and another that listens on the GitHub source and deploys to S3.
This limits our Enterprise customers to around 100-150
There's no reason we need to leave them around. We can create the Source pipeline only when we have updates to push out or when a Dapp is first created.
UPDATE: This issue originally corresponded to both the Source pipelines and Build pipelines, but they actually include pretty different subsets of work. Source pipelines only need to run when they initially get the code (or when we push updates), Build pipelines need to run every time an enterprise customer pushes up fresh source which they want deployed to their URL. This issue now only corresponds to the work required for Source pipelines. The Build pipeline work is located at https://github.com/Eximchain/terraform-aws-abi-clerk/issues/42
Currently an Enterprise Dapp takes two pipelines at all times: One to deploy Source to GitHub, and another that listens on the GitHub source and deploys to S3.
This limits our Enterprise customers to around 100-150
There's no reason we need to leave them around. We can create the Source pipeline only when we have updates to push out or when a Dapp is first created.
UPDATE: This issue originally corresponded to both the Source pipelines and Build pipelines, but they actually include pretty different subsets of work. Source pipelines only need to run when they initially get the code (or when we push updates), Build pipelines need to run every time an enterprise customer pushes up fresh source which they want deployed to their URL. This issue now only corresponds to the work required for Source pipelines. The Build pipeline work is located at https://github.com/Eximchain/terraform-aws-abi-clerk/issues/42