Timeout handler : WaitPipelineRun only if we're ready to create TaskRuns #680
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.
Changes
We can save one goroutines per PipelineRun by starting the wait
goroutine just before creating TaskRuns.
It's a bit related to #674, but for
pipelinerun
, trying to reduce potential number of goroutines whenever we can. In the case ofpipelinerun
, we can wait a bit before starting thewait
, asWait
will take theStartTime
into account (which is created really early) — that way, if something fails to validate (Pipeline reference not found, …), we won't even create a goroutine./cc @shashwathi correct me if I'm wrong 👼 😝
Signed-off-by: Vincent Demeester [email protected]
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
[ ] Includes tests (if functionality changed/added)[ ] Includes docs (if user facing)See the contribution guide
for more details.