Split CI into products for better cost management
Problem to solve
Today, our entire CI is divided into two different tags:
small
and large
.
This brings problems when using AWS cost management as all machines are tagged with the common
product.
In order to be able to know in a more accurate way how much CI every product is using, we need to split the CI.
Intended users
- Developers
- Managers
Permissions and Security
N/A
Proposal
Split our current CI:
small
large
Into:
airs-small
common-small
docs-small
integrates-small
melts-small
observes-small
reviews-small
skims-small
sorts-small
airs-large
common-large
docs-large
integrates-large
melts-large
observes-large
reviews-large
skims-large
sorts-large
Test plan
-
Release the new CI one product at a time -
Review AWS cost manager tags
Steps
-
Make sure that the code contributions checklist has been followed.
What does success look like, and how can we measure that?
-
CI completely updated -
CI split -
All products using new CI -
AWS Cost manager tags working -
CI deploy job re-enabled -
Update CI docs and add how to tune a product CI
Links / references
Edited by Daniel Salazar