Docker executor users can output the max memory consumed by a job by adding the following step to their config:
command: cat /sys/fs/cgroup/memory/memory.max_usage_in_bytes
This step should be added as the last step in your job, to identify the max usage after all of the steps have completed.
Note: This will be accurate if the job has one Docker image. Multiple Docker image builds will only report the memory usage of the primary image.
Memory usage will be reported in bytes. You can convert to GiB using your favorite search engine to check it against the amount of RAM available to your job, according to its assigned resource class.
This can help troubleshoot out-of-memory (OOM) errors.
To log memory usage over time for both Docker and machine executors, you can also add this step as the first step in your job:
while true; do