Pipelines kills idle Maven connections after 5 minutes

Pipelines started closing idle Maven connections that are idle for more than 5 minutes after the last infrastructure update. This affects any build which is running Maven and takes longer than this amount of time because such build will fail with 'connection reset socket exception'.

Some plugins in the Maven lifecycle are triggered after running integration tests and the only workaround is to force Maven to use a new connection on every request using 'mvn -Dmaven.wagon.http.pool=false clean install'. This, however, affects the build time.

I would like Pipelines to work the same way as they worked before because changes like these are either polluting the build yaml script with ugly workarounds or causing previously passing builds to fail for no reason.