On Sun, May 31, 2026 at 11:52:29PM +0200, Leopold Palomo-Avellaneda wrote: > Hi, > > > I'm trying to help in packaging of fastdds [1]. It is a small monster > package. > > After update all the patches to the new version, I pushed it to salsa. > However, I have not been able to built it because timeout. > > I have modified the timeout in the project to 4h, however, still the limit > of 3h still is applied. > > I have configured a runner in my university to build the package. They > connect to my runner, use the same image as salsa, but it fails because: > > /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. > 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 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
signature.asc
Description: PGP signature
