SAST fails: context deadline exceeded

Summary

The sast job fails because the execution of one of the analyzers take more than 10 minutes.

It's more likely to occur when performing SAST on a Java project because the analyzer builds the project prior to running Find Security Bugs.

Steps to reproduce

Configure SAST on a Java Maven project where the execution of mvn compile takes more than 10 minutes.

Example Project

https://gitlab.zendesk.com/agent/tickets/99479

What is the current bug behavior?

SAST fails with this error message:

context deadline exceeded

What is the expected correct behavior?

SAST succeeds. No timeout.

Possible fixes

Make it possible to adjust the timeout using a command line or an environment variable.

Also, it could be relevant to increase the default value of the timeout.

cc @plafoucriere