dosubot[bot] commented on issue #8581: URL: https://github.com/apache/incubator-devlake/issues/8581#issuecomment-3312229578
<!-- Greeting --> Hi @AldrinAJ! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the incubator-devlake team. <!-- Answer --> The error you're seeing (`context deadline exceeded (Client.Timeout exceeded while awaiting headers)`) means DevLake's API client isn't getting a response from Jenkins within the configured timeout window. This is common with Jenkins multi-branch pipelines, which can generate large API responses and slow down requests. DevLake's Jenkins integration uses a configurable timeout and retry mechanism for API calls. The default timeout is 120 seconds, and the default max retries is 3, but both can be increased via the `API_TIMEOUT` and `API_RETRY` configuration options. If Jenkins is slow or the dataset is large, you may need to set a much higher timeout value (for example, 5-10 minutes) and consider increasing retries further. You can set these in your environment or pipeline config—see the relevant code for details on how these are applied [`api_client.go`](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/helpers/pluginhelper/api/api_client.go), [`api_async_client.go`](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/helpers/pluginhelper/api/api_async_client.go). The scheduler that runs subtasks uses a ticker to pace execution, and its tick interval can be tuned. If you have a very large number of subtasks, consider reducing the scope of each pipeline run or splitting large jobs into smaller batches to avoid overwhelming Jenkins and DevLake's worker pool [`worker_scheduler.go`](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/helpers/pluginhelper/api/worker_scheduler.go). Also, make sure your Jenkins plugin scope-config is set up correctly, especially for multi-branch pipelines. Regex patterns for deployment stages (`deploymentPattern`, `productionPattern`) are required for proper data collection. Without these, some data may not be fetched as expected [`issue #8297`](https://github.com/apache/incubator-devlake/issues/8297). If you've already increased timeouts and retries but still see failures, try optimizing Jenkins server performance, reducing the number of branches/jobs fetched per run, or checking Jenkins logs for bottlenecks. There are no recent code changes or issues directly addressing this, so these configuration and operational adjustments are your best bet for now. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/477f6c5e-a044-4850-b6f1-0ac44fc225a8?feedback_type=other)</sup> [](https://app.dosu.dev/b4e8e847-d479-4541-83a8-d88d83fea5c9/ask?utm_source=githu b) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/incubator-devlake/issues/8581) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
