Colin Baumgarten 172dfe8d00 ci: Set job-level timeout for long-running jobs ...

The visualstudio jobs typically take longer than the gitlab
default project-level timeout of 1h.

This can cause build failures when a fork is created as part of
a merge request, because the fork will use the default project-level
timeout.

Set a job-level timeout of 2h which will override the project-level
one according to https://docs.gitlab.com/ci/yaml/#timeout to
eliminate the need to manually adjust the project-level timeout in
forks.

Signed-off-by: Colin Baumgarten <colin.baumgarten@hubersuhner.com>
Reviewed-by: Jakub Jelen <jjelen@redhat.com>
Merge-Request: <https://gitlab.com/libssh/libssh-mirror/-/merge_requests/826>

2026-05-04 14:24:46 +02:00

..

default.md

ci: Set job-level timeout for long-running jobs

2026-05-04 14:24:46 +02:00