Reputation: 593
I have a successful setup of a GitLab CI project with a private runner. Suddenly, the CI steps take over 4 minutes, instead of 20-25 seconds. I cannot pinpoint the increase in time. Could it be, that somewhere a timeout is being hit? by accessing a folder/network etc?
My CI project has a simple gcc
command, nothing fancy at all.
Any thoughts/experiences with this?
Upvotes: 6
Views: 14408
Reputation: 16487
Timestamps in Gitlab CI are still an open issue (#22745). However you could measure it with ts
from moreutils
, in bash you can pipe all the output through it with exec > >(ts ) 2>&1
. Example for ubuntu image follows:
ts:
image: ubuntu:latest
before_script:
- apt-get update
- apt-get install -qq moreutils
- exec > >(ts ) 2>&1
script:
- >
for I in {1..10}; do
sleep $((RANDOM % 10))s;
echo $I;
done
Upvotes: 1