[JIRA] (JENKINS-58921) Extremly slow build after connection to network
Title: Message Title Michal Zajac updated an issue Jenkins / JENKINS-58921 Extremly slow build after connection to network Change By: Michal Zajac Hi, When I changed network settings of my Virtual Machine to "Bridged: Connected directly to the physical network", jobs is done extremely slow.I have Jenkins server which is installed on Virtual Machine, when the IP of virtual machine is "local" (e.g. 192.168.1.20) jobs are done quite OK (~6minutes per build).But when I changed IP to domain IP (e.g. 3.194.15.23) build are s slow (up to 15 hours!). I changed IP due to fact, that I want to connect with server (from web browser) from every computer in network (not only from VM host computer)I tried almost everything, changed proxy setting, changed Java proxy settings, increase Java buffers, turn off the antyvirus and still nothing.This is not compiler/computer issue, because when I start compiling from command prompt (directly where the Makefile is), clean is perform quick, via Jenkins it stuck first time at:_mkdir -p XmlConfig_and take ~3minutes when in "normal" build it take ~100msany ideas where is the bug? UPDATE: When I change the IP settings in windows, and when there is no communication to e.g. SVN, compilation works fine (of course its not solve my problem)So my guessing is that this is some buffer in Jenkins after connection to WAN? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58921) Extremly slow build after connection to network
Title: Message Title Michal Zajac updated an issue Jenkins / JENKINS-58921 Extremly slow build after connection to network Change By: Michal Zajac Hi, When I changed network settings of my Virtual Machine to "Bridged: Connected directly to the physical network", jobs is done extremely slow.I have Jenkins server which is installed on Virtual Machine, when the IP of virtual machine is "local" (e.g. 192.168.1.20) jobs are done quite OK (~6minutes per build).But when I changed IP to domain IP (e.g. 3.194.15.23) build are s slow (up to 15 hours!). I changed IP due to fact, that I want to connect with server (from web browser) from every computer in network (not only from VM host computer)I tried almost everything, changed proxy setting, changed Java proxy settings, increase Java buffers, turn off the antyvirus and still nothing.This is not compiler/computer issue, because when I start compiling from command prompt (directly where the Makefile is), clean is perform quick, via Jenkins it stuck first time at:_mkdir -p XmlConfig_and take ~3minutes when in "normal" build it take ~100msany ideas where is the bug? UPDATE: When I change the IP settings in windows, and when there is no communication to e.g. SVN, compilation works fine Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Googl
[JIRA] (JENKINS-58921) Extremly slow build after connection to network
Title: Message Title Michal Zajac created an issue Jenkins / JENKINS-58921 Extremly slow build after connection to network Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-08-14 10:30 Environment: Windows 7 Priority: Blocker Reporter: Michal Zajac Hi, When I changed network settings of my Virtual Machine to "Bridged: Connected directly to the physical network", jobs is done extremely slow. I have Jenkins server which is installed on Virtual Machine, when the IP of virtual machine is "local" (e.g. 192.168.1.20) jobs are done quite OK (~6minutes per build). But when I changed IP to domain IP (e.g. 3.194.15.23) build are s slow (up to 15 hours!). I changed IP due to fact, that I want to connect with server (from web browser) from every computer in network (not only from VM host computer) I tried almost everything, changed proxy setting, changed Java proxy settings, increase Java buffers, turn off the antyvirus and still nothing. This is not compiler/computer issue, because when I start compiling from command prompt (directly where the Makefile is), clean is perform quick, via Jenkins it stuck first time at: mkdir -p XmlConfig and take ~3minutes when in "normal" build it take ~100ms any ideas where is the bug?
