GLAS | Configure default timeout to 3 hours

Summary

Increase default timeout for GitLab Advanced SAST analyzer to 3 hours to accommodate large project scans.

Problem

GitLab Advanced SAST analyzer is experiencing timeout issues when scanning large projects with the current timeout configuration. This results in:

• Failed pipeline executions
• Incomplete security scans
• Teams unable to get SAST results for larger codebases

Proposed Solution

Increase the default timeout value to 3 hours (180 minutes), which is the maximum available timeout on self-hosted runners.

Impact

• Positive: Large projects will complete SAST scans successfully
• Negative: Longer pipeline execution times for projects that hit timeout scenarios
• Mitigation: Only affects projects that were previously timing out

Implementation

Update the default timeout configuration in the GitLab Advanced SAST analyzer settings.