Gitlab Projects: CI Pipelines¶
All projects on the Dropsolid Experience Cloud Platform have access to the shared runners of the Platform via the built-in Gitlab CI/CD capabilities.
The CI/CD capabilities should be used to run typical CI jobs, like code quality checks, artifact generation, ... They should not be used to deploy code, see below.
Those runners are dedicated ephemeral instances that are only used once, and cannot be re-used.
These instances have following specs:
- 2 vCPU
- 4 GB RAM
- 50 GB disk
Why only CI and not CI/CD?¶
Platform itself handles deployments, including deploying the artifacts your CI pipeline builds via the Artifact deployment method. Therefore, these pipelines should only be used for continuous integration.
You can find the official Gitlab pipeline documentation here.
Limitations¶
- 300 CI minutes per month per project (fair use)
- Maximum artifact size: 250MB (hard cap)
- Artifact expiration: 30 days (hard cap, latest artifact from most recent successful pipeline remains available indefinitely)
- Job expiration: 1 year (hard cap)