Inherit CI timeout setting when forking repository

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Description

Currently, the Inkscape build time is approximately 1hour and 5 minutes without ccache presence, which causes most PR pipelines people do to fail because the CI timeouts after an hour. Since the forked project is owned by the contributor, maintainers cannot change the CI timeout setting on the fork and cannot relaunch the pipeline job. The only option is for the contributor to change its settings in his fork.

Proposal

Would it be possible to either

• Ideally, inherit the CI timeout value when forking
• or add a .gitlab-ci.yaml option to specify a CI timeout that would override the project's time so that projects can configure that and it would be passed in the fork

Links / references