Welcome to Jenkins v2! Click here to install additional features you need

s/Jenkins v2/Jenkins 2

s/you need/

Also, I'd like a yellow roof for the bikeshed.

batmat 2 Minutes seems to still be pretty long. Could you take a few more stack traces during that time (also the second 30 seconds), maybe there's still a code path to a connection without custom timeout?

Or WDYT of shorter timeouts such as 10s? Also, what happens in Jenkins 1.x when you "test" the proxy configuration without having defined a proxy? Does it also take long (according to https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/ProxyConfiguration.java#L332 it should be 30 seconds)?

batmat can we move the discussion of the terminology for 'upgrading' jenkins 1 to 2 to this ticket: JENKINS-33663 ? there will be changes to the procedure, and I think text changes are appropriate to be included there. If you are seeing this banner with a NEW installation, there's a bug, it's not supposed to happen, which is why the term 'upgrading' is included.

Could you verify the latest build addresses both of the excessive wait time issues for you I've lowered the default timeout to 20 seconds? You should expect to see: 20 second wait time at first, and a 20 second wait time when first loading the wizard. We could lower it more, I don't know what a reasonable minimum is, though... even 10 seconds seems long to me... either Jekins can connect to an external site in 10 seconds or there are probably some network issues, that's probably a decision for a different ticket.

https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/4517/artifact/war/target/jenkins.war

New screencast made with 1417cd37b8e83030ee9d4b7ff0e4a349 (https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/4523/artifact/war/target/jenkins.war)

https://dl.dropboxusercontent.com/u/6790263/JENKINS-33557-1417cd37b8e83030ee9d4b7ff0e4a349.ogv

kzantow and bug confirmed, then. See screencast. I filed JENKINS-33767 about that.

IMO, the first timeout/part can be considered resolved. The second part still takes roughly 45 seconds.

Way to go anyway, it's heading in the right direction.

And re-reading myself, I didn't answer: I also think that 10, or say 15, seconds should always be sufficient.

Code changed in jenkins
User: kzantow
Path:
core/src/main/java/hudson/model/UpdateCenter.java
http://jenkins-ci.org/commit/jenkins/52c4ed6da03ea02cff54f7a31dad62c55d6e8c94
Log:
JENKINS-33557 - tcp timeouts cause installer to hang for 6 minutes

Code changed in jenkins
User: kzantow
Path:
core/src/main/java/hudson/Functions.java
core/src/main/java/hudson/model/Descriptor.java
core/src/main/java/hudson/model/ManageJenkinsAction.java
core/src/main/java/hudson/tools/ToolDescriptor.java
core/src/main/java/jenkins/install/SetupWizard.java
core/src/main/java/jenkins/management/ConfigureLink.java
core/src/main/java/jenkins/model/GlobalConfiguration.java
core/src/main/java/jenkins/model/GlobalConfigurationCategory.java
core/src/main/java/jenkins/model/Jenkins.java
core/src/main/java/jenkins/mvn/GlobalMavenConfig.java
core/src/main/java/jenkins/tools/GlobalToolConfiguration.java
core/src/main/java/jenkins/tools/ToolConfigurationCategory.java
core/src/main/resources/hudson/logging/LogRecorder/sidepanel.jelly
core/src/main/resources/hudson/logging/LogRecorderManager/index.jelly
core/src/main/resources/hudson/logging/LogRecorderManager/sidepanel.jelly
core/src/main/resources/hudson/model/ComputerSet/index.jelly
core/src/main/resources/hudson/model/ComputerSet/sidepanel.jelly
core/src/main/resources/hudson/model/Job/configure.jelly
core/src/main/resources/hudson/model/Label/sidepanel.jelly
core/src/main/resources/hudson/model/UpdateCenter/sidepanel.jelly
core/src/main/resources/hudson/model/User/sidepanel.jelly
core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/index.jelly
core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/sidepanel.jelly
core/src/main/resources/jenkins/install/SetupWizard/authenticate-security-token.jelly
core/src/main/resources/jenkins/install/pluginSetupWizard.properties
core/src/main/resources/jenkins/management/Messages.properties
core/src/main/resources/jenkins/tools/GlobalToolConfiguration/index.groovy
core/src/main/resources/lib/hudson/project/configurable.jelly
test/src/test/java/hudson/model/HudsonTest.java
test/src/test/java/hudson/tasks/MavenTest.java
test/src/test/java/hudson/tools/JDKInstallerTest.java
war/src/main/js/api/plugins.js
war/src/main/js/pluginSetupWizardGui.js
war/src/main/js/templates/progressPanel.hbs
war/src/main/less/pluginSetupWizard.less
war/src/main/webapp/css/style.css
http://jenkins-ci.org/commit/jenkins/2fbf73fc76e32698c7d9f8b17cf7325d96fa5513
Log:
Merge remote-tracking branch 'primary/2.0' into JENKINS-33557-tcp-timeouts-during-install

Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/java/hudson/ProxyConfiguration.java
core/src/main/java/hudson/model/UpdateCenter.java
test/src/test/java/hudson/model/UpdateCenterConnectionStatusTest.java
http://jenkins-ci.org/commit/jenkins/ee5c1a3a133e203f0296c3238798b4a7c5b92b8e
Log:
Merge pull request #2156 from kzantow/JENKINS-33557-tcp-timeouts-during-install

JENKINS-33557 - connectivity checks may cause setup wizard to hang for a long time

Compare: https://github.com/jenkinsci/jenkins/compare/6a74607b4ef0...ee5c1a3a133e

Timeouts have been reduced and made configurable, I think we can close this? batmat kzantow?

+1 from me danielbeck, though there's probably still some room for improvement, it's now perfectly usable. And as we're talking about a one-shot screen I guess it's enough for now.
Thanks