Here's what I'm getting in my builds:
1Build started
2git config --global core.autocrlf input
3git clone -q --branch=master git@github.com:AcklenAvenue/maxorwebsite.git C:\projects\maxorwebsite
4ssh: connect to host github.com port 22: Bad file number
5fatal: Could not read from remote repository.
6
7Please make sure you have the correct access rights
8and the repository exists.
9git clone -q --branch=master git@github.com:AcklenAvenue/maxorwebsite.git C:\projects\maxorwebsite
10ssh: connect to host github.com port 22: Bad file number
11fatal: Could not read from remote repository.
12
13Please make sure you have the correct access rights
14and the repository exists.
15git clone -q --branch=master git@github.com:AcklenAvenue/maxorwebsite.git C:\projects\maxorwebsite
16ssh: connect to host github.com port 22: Bad file number
17fatal: Could not read from remote repository.
18
19Please make sure you have the correct access rights
20and the repository exists.
21Command exited with code 128

#1 Posted by byron on 29 Sep, 2014 09:50 PM
This is happening on all builds that pull from github.
#2 Posted by Feodor Fitsner Support staff on 29 Sep, 2014 09:55 PM
I'm looking into that.
Seems like connectivity issues inside VMs. Might be sporadic Azure problem.
#3 Posted by Huy Nguyen on 29 Sep, 2014 10:08 PM
I'm getting the same problem with BitBucket. I'm able to pull the source from bit bucket https channel just fine
#4 Posted by byron on 29 Sep, 2014 10:15 PM
It might be a side-effect, but looks like no builds are running right now. They stay in the queued state.
#5 Posted by Feodor Fitsner Support staff on 29 Sep, 2014 10:16 PM
Yes, VM provisioning has slowed down too. We are moving to another region.
#6 Posted by byron on 29 Sep, 2014 10:19 PM
That is SO cool how you can pick up your whole network and just say, "we are moving to another region."
#7 Posted by Feodor Fitsner Support staff on 29 Sep, 2014 10:21 PM
Cool, but exhausting :(
#8 Posted by byron on 29 Sep, 2014 10:22 PM
Automate all the things!
#9 Posted by byron on 29 Sep, 2014 10:33 PM
Can you give an ETA on the fix?
#10 Posted by Feodor Fitsner Support staff on 29 Sep, 2014 10:38 PM
It could take up to 1 hour to copy image to another region. Though it could start working in this region sooner. Sorry for that interruption.
#11 Posted by byron on 29 Sep, 2014 10:39 PM
Thanks for the update!
#12 Posted by Feodor Fitsner Support staff on 30 Sep, 2014 12:52 AM
Should be OK now.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:48 AM.