chore: increase build timeout to 90 minutes (#2139) backport for 8.1

[mdelapenya]

Backports the following commits to 8.1:

• chore: increase build timeout to 90 minutes (chore: increase build timeout to 90 minutes #2139)
• ci: increase log rotation (ci: increase log rotation #2138)

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-02-28T21:44:19.965+0000

• Duration: 75 min 49 sec

Test stats 🧪

Test	Results
Failed	5
Passed	267
Skipped	0
Total	272

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:container-in-pod" 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:cronjob-container": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-failing-pod": context deadline exceeded 

• no stacktrace

Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:redis": context deadline exceeded 

• no stacktrace

Steps errors

Expand to view the steps failures

Shell Script

• Took 44 min 23 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2184-3-e289be0e-5b1a-4951-92e8-2c2c83af99a3/e2essh [email protected] -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh "elastic-agent && ~@nightly && ~@skip:amd64" '

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-02-28T22:59:02.405Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from running pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Logs collection from failing pod – elastic-agent standalone
• Name: Initializing / End-To-End Tests / kubernetes-autodiscover_debian_amd64_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.