[release-1.1] Increase prow timeout to 1h15m #1049
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is this a bug fix or adding new feature?
What is this PR about? / Why do we need it? This is a bandaid fix to get 1.1.4 out. Our build time has been steadily increasing and now it consistently breaches the 1h timeout. https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/aws-ebs-csi-driver-push-images. It was already very slow before compared to github actions (30-45 mins vs 15mins) so it will need to be fixed, tracking it here: #1048
for comparison master branch is still pretty slow at 40 mins but it building for windows in addition to x86 and arm! So one option to solve #1048 is to backport the Makefile/Dockerfile/build changes to release-1.1 branch.
What testing is done?