In my Jenkins setup, we have a 6 hour long test suite running on a separate agent machine. After each test execution it will bundle all the results with a screenshot (bundle everything as a JSON) and send it to a 3rd party reporting server as an API call.
But sometimes after 30 -40 minutes of execution, the Jenkins job will get stuck where it's sending JSON data to a 3rd party server.
At the same time if I do the same API call using postman, it works fine, but through Jenkins it's not sending properly.
This might be due to some network policy or restriction or due to a security scanner, but how am I going to resolve it.
Where should I start?
I'm 100% sure it's not about the resource issue. There is no any specific pattern on which test case is stuck. Jenkins agent also up and running.