Re: Understanding CI in Salsa, timeouts and runners

El 1/6/26 a les 16:38, Antonio Terceiro ha escrit:
> On Sun, May 31, 2026 at 11:52:29PM +0200, Leopold Palomo-Avellaneda wrote:
[...]

>>
>> /usr/bin/bash: line 273: cd: /builds/robotics-team/fastdds/debian/output: No
>> such file or directory
>> WARNING: after_script failed, but job will continue unaffected: exit code 1
>>
>> So,
>>
>> 1) Can we use a private runner to a salsa project to build a packages, at
>> least in testing?
> 
> Sure, you can use whatever runner you want.

Ok, but it fails when try to build in my own runner. Why? I'm using the 
same image from salsa. Should I configure something more?


>> 2) How can I increase or how can we manage to build packages that needs a
>> lot of time to be built?
> 
> There is a runner timeout that is used whenever it's smaller than the
> project/job timeout. 3h is probbaly the default runner timeout.
> 
> https://docs.gitlab.com/ci/runners/configure_runners/#set-the-maximum-job-timeout

So, you can put a small number than that, not a bigger than the default 
runner timeout.

> There is an existing support request to raise this timeout, and we'll
> get to it at some point. If you are in a hurry and can't wait, you can
> probably just use your own private runner.
> 
> https://salsa.debian.org/salsa/support/-/work_items/587

If we have a timeout problem, we create a work item or add to this one?

Best regards,

Leopold

-- 
--
GPG: 05F4A7A949A2D9AA
Catalonia
-----------------------------------------------------------
Si us plau, escriviu la resposta després del text original.

Please write your reply below the original message.