Repository navigation
[CI] Increase timeout settings in integration trigger script - #17424
Merged
Merged
Conversation
Updated the timeout values for integration tests in the trigger script to allow for longer execution times. The timeout for individual package tests was increased from 240 to 300 minutes, and the duration for AWS and GCP authentication plugins was extended from 10800 to 18000 seconds.
💔 Build Failed
Failed CI Steps
History
cc @mrodm |
kcreddy
approved these changes
Feb 17, 2026
Contributor
🚀 Benchmarks reportTo see the full report comment with |
kpollich
approved these changes
Feb 17, 2026
Collaborator
Author
|
Merging this PR, since failures in CI are unrelated to this change |
jakubgalecki0
pushed a commit
to jakubgalecki0/integrations
that referenced
this pull request
Feb 19, 2026
…#17424) Updated the timeout values for integration tests in the trigger script to allow for longer execution times. The timeout for individual package tests was increased from 240 to 300 minutes, and the duration for AWS and GCP authentication plugins was extended from 10800 to 18000 seconds. Update the timeout and liftime settings in the serverless pipelines up to 6 hours too.
navnit-elastic
pushed a commit
to navnit-elastic/integrations
that referenced
this pull request
Mar 2, 2026
…#17424) Updated the timeout values for integration tests in the trigger script to allow for longer execution times. The timeout for individual package tests was increased from 240 to 300 minutes, and the duration for AWS and GCP authentication plugins was extended from 10800 to 18000 seconds. Update the timeout and liftime settings in the serverless pipelines up to 6 hours too.
This was referenced Mar 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed commit message
Increase timeout settings in integration trigger script up to 5 hours.
Updated the timeout values for integration tests in the trigger script to allow for longer execution times. The timeout for individual package tests was increased from 240 to 300 minutes, and the duration for AWS and GCP authentication plugins was extended from 10800 to 18000 seconds.
Related issues