How does Mint CI's DAG-based execution differ from traditional parallelization in other CI systems?
Mint CI's DAG-based execution automatically determines the optimal execution order and runs everything that can run in parallel by expressing task dependencies. Unlike traditional CI which often repeats work across virtual machines or requires manual parallelization, Mint CI only rebuilds what has changed and reuses cached results based on filesystem contents, leading to more efficient and faster builds.
Can I debug a failing CI task directly within the Mint CI environment?
Yes, Mint CI allows engineers to SSH directly into running tasks. This capability enables remote debugging with local changes included, providing a powerful way to diagnose and fix issues without guessing from truncated logs, which is a significant advantage over many traditional CI systems.
What is the billing model for compute resources, and how does it handle variable task requirements?
Mint CI bills compute resources by the second, with a 1-minute minimum per agent size per run. It allows users to specify CPU and memory per task, meaning you only pay for the resources actually needed for each specific task. This contrasts with traditional CI, where you often pay for a fixed runner size for an entire job, regardless of individual task requirements.
How does Mint CI manage and optimize test suites, particularly for flaky tests?
Mint CI includes robust test suite management. It can automatically detect, quarantine, and track flaky tests, allowing teams to continue shipping while the root causes are addressed. For Pro users, it offers analytics on problematic flaky tests and trends in test performance, with automatic re-balancing of parallel test suite partitions based on recent performance.
What are the storage and data transfer allowances included with Mint CI, and how are additional usages billed?
Mint CI provides 100 GB of cache storage and 10 GB of artifact storage for free, with additional allocations increasing based on compute usage. It also includes 25 GB of external data transfer per month, with further increases tied to compute hours. Additional cache and artifact storage are billed at $0.00164 per GB per day, while additional data transfer is $0.15 per GB.
Does Mint CI support custom container image builds, and how does it handle Dockerfiles?
Yes, Mint CI supports building container images both with and without a Dockerfile. This flexibility allows teams to integrate their existing containerization strategies or leverage Mint CI's capabilities for image creation directly within their CI/CD workflows.