How much storage or resources are needed for our Git, Build, and Work Item Management systems?
Beyond the basic installation footprint of those three ALM applications, the main disk footprint comes from the…
-
DataStage Assets, and
-
MettleCI Unit Test data files
…that land on disk at various point in their lifecycles.These will affect disk utilisation on…
-
the Git host; where their Git repositories will manage versions of DataStage and MettleCI Unit Test assets
-
the DataStage Client host; where Bamboo Agents will execute the MettleCI-enabled CI / CD actions that depend on DataStage command line tools (e.g. importing Jobs into a target DataStage instance; and
-
the DataStage Engine host where MettleCI’s Workbench and Unit Test Harness components are installed (i.e. the Engine where the customer does their Job development).
For #1 above, you could check the size of the Projects directory on the development DataStage Engine host and add a growth margin based on the customer’s future plans for their DataStage-based solutions.However, for #2 it simply isn’t possible to predict the number, size and growth rate of Unit Tests. Therefore, customers should actively monitor…
-
the size of the MettleCI home directory on the Engine Tier host; and
-
changes to the Git repositories
…to ensure they don’t run out of whatever storage they’ve allocated. (edited)
The general points above apply for any Git repository management and CI / CD platforms, not just the Atlassian ones.