gradle / gradle/develocity-build-validation-scripts
The scripts should expose an option to increase the timeout
- Dominant language
- Shell
- Stars
- 115
- Forks
- 23
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 6
Description
Under certain conditions (e.g. a lot of data, CPU load on Develocity server), uploaded build scans can take a while to fully process. During the last step "Merge build results", the previously-uploaded build scans cannot be retrieved. I believe the retrieval process has a timeout of 10 seconds by default. Allow the end user to provide a custom timeout to work around this issue e.g. via `--timeout`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the repository's script entry points and trace the “Merge build results” step where previously uploaded build scans are retrieved. Locate how the retrieval timeout is configured, then consider the issue complete when users can provide --timeout and that value controls the retrieval wait.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100