The Travis-CI.org has a 50 minutes job timeout. However building the complete dependences from source takes about 30 minutes and the tests takes about 30 minutes too. as the result, if there is not cached built dependencies (when a new branch is added, or testing environment variable changes) all jobs will timeout after 50 minutes resulting an error in the build.
current solution is to utilize the bate feature on travis that prepares cache that contains the built dependencies in the first build stage then run the testing stages, each of the stage will be in different jobs of 50 minutes limits, and effectively avoid the timeout problem.
The Travis-CI.org has a 50 minutes job timeout. However building the complete dependences from source takes about 30 minutes and the tests takes about 30 minutes too. as the result, if there is not cached built dependencies (when a new branch is added, or testing environment variable changes) all jobs will timeout after 50 minutes resulting an error in the build.
current solution is to utilize the bate feature on travis that prepares cache that contains the built dependencies in the first build stage then run the testing stages, each of the stage will be in different jobs of 50 minutes limits, and effectively avoid the timeout problem.