Job timeout configuration and plan-tier hard limits

Job Timeout Enforcement

In the .travis.yml specification, the timeout configuration allows for the definition of a maximum duration for a build job. When a job exceeds this specified limit, the system terminates the process and marks the build status as failed.

There is an inherent interaction between these user-defined values and the hard limits imposed by different Travis CI plan tiers. While a user may specify a duration in the configuration, the underlying infrastructure enforces a ceiling based on the account type (e.g., Free versus Paid plans).

Configuration Uncertainty

It is unclear how the system prioritizes these two constraints when they conflict. Specifically, if a user-defined timeout exceeds the plan's maximum allowable duration, the behavior of the termination signal and the resulting build status requires clarification.

• Does the plan-tier hard limit override the .travis.yml timeout value?
• Is the build status reported as a timeout failure or a system-level termination when the plan limit is hit?