High latency networks add extra time to a job completion

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When a Jenkins agent is added to a cluster and a job is assigned to it, this job will take some extra time to complete regardless of what the job does. Testing with an empty job on a network with high latency (75ms roundtrip) caused an additional *45 second*s for the empty job to succeed. looking a the console we noticed that the job is not doing any computation.

            Assignee:
            Carlos Sanchez
            Reporter:
            Manuel Corona
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: