Skip to content

Commit 69d7204

Browse files
authored
docs: add cost estimation for a realistic pipeline (#395)
Co-authored-by: kayma <kayma@hlag.com>
1 parent 9ef04b1 commit 69d7204

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,18 @@ By default the module creates a a cache for the runner in S3. Old objects are au
158158

159159
Creation of the bucket can be disabled and managed outside this module. A good use case is for sharing the cache across multiple runners. For this purpose the cache is implemented as a sub module. For more details see the [cache module](https://github.com/npalm/terraform-aws-gitlab-runner/tree/develop/cache). An example implementation of this use case can be found in the [runner-public](https://github.com/npalm/terraform-aws-gitlab-runner/tree/__GIT_REF__/examples/runner-public) example.
160160

161+
## Cost Estimation
162+
163+
### Hapag-Lloyd AG
164+
We set up a build pipeline for 13 developers (plus one technical user running Renovate to update all
165+
dependencies) in 3 availability zones. Running 2 different type of machines. One for cloud deployment,
166+
aka `terraform apply` (t3.medium, on demand, 3 idles, 15 max, 45 minutes idle time). The other one
167+
for all other jobs (c5.xlarge, spot, 9 idles, 60 max, 45 minutes idle time). All machines are
168+
using a shared S3 cache. The pipeline is running from 7am till 7pm. In the non peak hours all
169+
docker+machine instances are killed.
170+
171+
Per day costs: $20. We are quite satisfied with this pipeline.
172+
161173
## Usage
162174

163175
### Configuration

0 commit comments

Comments
 (0)