configure the timeout option for the exec command when running as a service

I have some builds which occasionally fail due to a CI Timeout error.

I am wondering how/if I can configure my runner to use a different timeout option, when running as a service . I can see that I can specifiy the command when running gitlab-ci-multi-runner exec shell --timeout 999 but I'm not sure how/if this can be translated to the gitlab-ci-multi-runner run command used when running as a service.

Can this be done from the .toml config file? or as a parameter to the gitlab-ci-multi-runner "run"?

If not, support for this would be very useful for me 😃

I am slightly confused about setting the timeout. More details about this would be appreciated. Especially since my builds timeout after 3600s, while the DefaultTimeout = 7200 according to consts.go. I see the run command takes this DefaultTimeout if the timeout is <= 0.

Setting this value from the .toml config (to override or force) would be appreciated.

@ayufan @tmaczukin

Hey guys

I also get following error ERROR: Build failed: execution took longer than 3600 seconds

I run my builds exclusively on ec2 and my build went above 1 hr but it was going on successfully and not hung process or anything like that. Can I configure and increase this limit in configuration somehow.

Thx

cc @ty-dev

Would like to add;

If the base image for dockerfile is big; the build get really slow under dind service and with no way to cache; thing get further messy. Maybe will dig into this issue on separate issue. But right now info about timeout will be appreciated.

Thx @ayufan @tmaczukin

cc @ty-dev

mentioned in issue #1487

You can set the timeout in your project settings in GitLab. Go to your project -> Edit Project -> Builds section. You can set timeout in minutes there.

DefaultTimeout from const.go is set only if GetBuildResponse received from GitLab contains timeout value that is equal or less than 0. And by default a new project in GitLab has this setting set to 60 minutes.

@tmaczukin

Opps Thx man; u r the best 😄 And it was right in front of me 😛

Thx again

Milestone changed to %v1.7

Status changed to closed

No such option 😢 Go to your project -> Edit Project -> Builds section. Where to find ??

@sachingpta It was moved some time ago into the CI/CD Pipelines setting page. It's few position above the Edit project 😉

mentioned in issue #1409 (closed)