Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs for connecting to Azure DevOps as a code host #8647

Closed
dadlerj opened this issue Feb 28, 2020 · 11 comments
Closed

Add docs for connecting to Azure DevOps as a code host #8647

dadlerj opened this issue Feb 28, 2020 · 11 comments
Assignees
Labels
docs estimate/1d planned/3.16 Issues that were planned for the given milestone. Used by cmd/tracking-issue. team/source Tickets under the purview of Source - the one Source to graph it all

Comments

@dadlerj
Copy link
Member

dadlerj commented Feb 28, 2020

From a user

I'm trying to configure repos from Azure DevOps using SSH authentication.

I tried following these instructions: https://docs.sourcegraph.com/admin/external_service/other

I'm a little foggy though. For starters, I don't know the SSH port number that Azure DevOps uses.

Do you have any more specific instructions specially for Azure DevOps?

Based on searching online, it looks like Azure DevOps only supports port 22 for SSH access, so no port number is required. References:

@uwedeportivo
Copy link
Contributor

Dear all,

This is your release captain speaking. 🚂🚂🚂

Branch cut for the 3.15 release is scheduled for tomorrow.

Is this issue / PR going to make it in time? Please change the milestone accordingly.
When in doubt, reach out!

Thank you

@keegancsmith keegancsmith modified the milestones: 3.15, 3.16 Apr 16, 2020
@tsenart tsenart added the planned/3.16 Issues that were planned for the given milestone. Used by cmd/tracking-issue. label Apr 28, 2020
@uwedeportivo
Copy link
Contributor

Dear all,

This is your release captain speaking. 🚂🚂🚂

Branch cut for the 3.16 release is scheduled for tomorrow.

Is this issue / PR going to make it in time? Please change the milestone accordingly.
When in doubt, reach out!

Thank you

@keegancsmith
Copy link
Member

@dadlerj, @tsenart I don't have any bandwidth for this, and have consistently dropped the ball on doing it. Is there someone more appropriate for this task?

@keegancsmith keegancsmith removed their assignment May 14, 2020
@keegancsmith keegancsmith removed this from the 3.16 milestone May 14, 2020
@christinaforney christinaforney added this to Backlog in Documentation Aug 6, 2020
@unknwon
Copy link
Member

unknwon commented Feb 24, 2021

Note: we now have working example on https://k8s.sgdev.org/site-admin/external-services/RXh0ZXJuYWxTZXJ2aWNlOjE0, should be helpful for whoever takes this.

@unknwon unknwon mentioned this issue Feb 24, 2021
14 tasks
@indradhanush indradhanush self-assigned this Mar 4, 2021
@apjanke
Copy link

apjanke commented Mar 16, 2021

Hi @unknwon and all! Can someone share how you got this working? I'm a new user and I've been trying to set up a local Sourcegraph 3.25.2 instance on Ubuntu 18.04 connected to our Azure DevOps repos, and having no luck.

I tried adding them as a generic Git host, like this:

{
  "url": "ssh://git@ssh.dev.azure.com:22/",
  "repos": [
    "v3/MYORG/Project1/Project1",
    "v3/MYORG/Project2/Project2",
    "v3/MYORG/Project3/Project3"
     ]
}

("MYORG", "Project1", "Project2", and "Project3" are bogus names, of course, for privacy)

and the repos show up in the list of our repos, but when I try to clone any of them, I just get this error:

Repository does not exist: ssh.dev.azure.com-22/v3/MYORG/Project1/Project1

I'm running Sourcegraph as a user which has an SSH key attached to a DevOps account that has access to these repos.

@unknwon
Copy link
Member

unknwon commented Mar 16, 2021

@apjanke We used HTTPS, I'm pretty sure SSH won't work because there is no way to specify which SSH key to use for Azure code host connections.

{
  "url": "https://{REDACTED}@sourcegraph.visualstudio.com/sourcegraph/_git/",
  "repositoryPathPattern": "sourcegraph.visualstudio.com/{repo}",
  "repos": [
    "Test%20Repo"
  ]
}

@apjanke
Copy link

apjanke commented Mar 16, 2021

@unknwon Darn. Were you using 2FA with your DevOps accounts? We have 2FA enabled for our Microsoft/Azure AD accounts, and I haven't been able to get HTTPS-based cloning working on Linux with that setup.

@unknwon
Copy link
Member

unknwon commented Mar 16, 2021

@apjanke Not sure about Azure DevOps, but GitHub allows using PAT as password when 2FA enabled, maybe that's also the case?

@apjanke
Copy link

apjanke commented Mar 16, 2021

@unknwon Aha, yes it does: https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=preview-page

I will give that a try.

@alexfogg
Copy link
Contributor

alexfogg commented Jul 1, 2021

Chiming in here that I think this would be a welcome addition - I've noticed a few questions coming in from prospective Sourcegraph customers lately to the CE team and to the SDRs around setting up ADO.

@unknwon
Copy link
Member

unknwon commented Jul 1, 2021

cc @ryphil for triage, also cc @flying-robot this was an onboarding task for Indra but we didn't get it prioritized, maybe give another try for the coming new hire?

@eseliger eseliger added team/source Tickets under the purview of Source - the one Source to graph it all and removed [deprecated]team/core-application labels Feb 4, 2024
@eseliger eseliger closed this as completed Feb 4, 2024
Documentation automation moved this from Backlog to Done Feb 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs estimate/1d planned/3.16 Issues that were planned for the given milestone. Used by cmd/tracking-issue. team/source Tickets under the purview of Source - the one Source to graph it all
Projects
Development

No branches or pull requests

9 participants