Details
-
Bug
-
Resolution: Invalid
-
Medium
-
None
-
5.0 M5
-
None
-
None
Description
If you configure a bitbucket repository, provide a username, but not a password, then if the build runs on an elastic agent the build will reliably hang on "initializing empty git repository". I haven't tried with mercurial.
It works fine on remote agents, I haven't tested local agents.
I did some digging and found that the agent was waiting for the response for "git ls-remote <URL>".
The agent logs looked like:
2013-04-18 07:39:42,370 INFO [tunnellogger-thread] [LocalAcceptor] [tunnelserver:26224-1-thread-36] Accepted a local connection on port 4527, tunnel age: 59s 2013-04-18 07:40:42,422 INFO [tunnellogger-thread] [LocalAcceptor] [tunnelserver:26224-1-thread-54] Accepted a local connection on port 4527, tunnel age: 55s 2013-04-18 07:41:42,372 INFO [tunnellogger-thread] [LocalAcceptor] [tunnelserver:26224-1-thread-50] Accepted a local connection on port 4527, tunnel age: 59s 2013-04-18 07:42:42,371 INFO [tunnellogger-thread] [LocalAcceptor] [tunnelserver:26224-1-thread-54] Accepted a local connection on port 4527, tunnel age: 59s 2013-04-18 07:43:42,442 INFO [tunnellogger-thread] [LocalAcceptor] [tunnelserver:26224-1-thread-55] Accepted a local connection on port 4527, tunnel age: 50s 2013-04-18 07:44:42,371 INFO [tunnellogger-thread] [LocalAcceptor] [tunnelserver:26224-1-thread-54] Accepted a local connection on port 4527, tunnel age: 59s
and in the server logs there were many message like:
2013-04-18 18:21:23,493 INFO [tunnel:443-46593] [DefaultTunnelStatusTracker] Unable to establish the tunnel connection. Retrying in 5s. Connection: Tunnel ec2-54-224-57-87.compute-1.amazonaws.com:46593 - (ec2-54-224-57-87.compute-1.amaz onaws.com:26224) - bamboo.extranet.atlassian.com:443
Attachments
Issue Links
- is related to
-
-
- Closed
-