Background
I have an Azure Synapse SQL server which have some tables and stored procedures. Visual Studio 2019 (VS2019) is connected to the SQL server using Active Directory Interactive Authentication with use name being a Service Account Email.
I have built a Azure DevOps Demo, with following setups (Organization, Project, Git Repository).
I have added the Service Account Email to the Azure DevOps project and repository level, with contributor access.
I am trying to synchronize the stored procedures with my Azure DevOps Repository.
I am able to use VS2019 > Team Explorer > Manage Connections, and set the Service Account Email as the "hosted repositories for", and see my Repositories appear in the list.
Problem
It turned out that when I try to push Git Changes, by Team Explorer > New Repository > Existing remote, where I entered the full URL of my repository https//dev.azure.com/%Organization%/%Project%/_git/%Repository%, following error turned up: Git failed with a fatal error. unable to access 'above URL': SSL certificate problem, unable to get local issuer certificate. How can I resolve this error?
How to push all of my existing stored procedures to my Repository?
Faced the same issue, requesting you to go through the link. Hope this will resolve the issue:
Authentication failed for https://xxx.visualstudio.com/DefaultCollection/_git/project
Related
I am trying to configure the git integration of Azure Data Factory to my Azure DevOps Git repo. The Dev Data Factory already exists, so I am trying to use the "configuration" process from the "Manage" menu.
When I press the "configure" button, I can select "repository type" (DevOps Git), and I can select my "Azure Active Directory", but the DevOps "organization name" is not displayed in the dropdown. If I use the repository link from my DevOps project, I get the following error
The Dev Ops repository link is invalid, URL must start with http or https and be in DevOps format. For example: https://account.visualstudio.com/project/_git/repository
Turns out our Git server is an "OnPrem" machine and the URL of our repo https://azuredevops.CompanyName.com/[organziation]/[project]/_git/repository
Is this a known error that ADF cannot integrate with a repo on a stand-alone server? Or are there some network settings that we need to enable/configure to make it work?
My company has an old local git repository, which I'm trying to add to Azure Devops but so far, I've been unsuccessful (I've never setup a repository in Devops before, so I'm very new to this).
I've been trying to add this to devops by going into Repos > Import Repository, however when I attempt to import, I receive the following error:
I know this repository exists because I'm able to open this repository url via visual studio and work with the project within there, however when I attempt to import it into azure devops, I'm receiving that issue.
I've tried both providing authentication username & PAT....and I've attempted with no authentication. Neither seems to work.
Any idea what I'm doing wrong to get this imported into devops?
Thanks
While importing from Bitbucket Server which is accessible over VPN to Azure DevOps, I am facing the issue as "Clone URL is incorrect. Clone URL requires authorization". May I know how to fix this issue.
And I saw import repository option in Azure DevOps. But is there any way to import multiple projects and their repositories of Bitbucket Server to Azure DevOps?
Here is a suggestion ticket about add support for Bitbucket Server for Azure DevOps. You can vote this ticket.
As a workaround, you can use git commands to clone and push your repositories.
1.Clone the source repo to a temporary folder on your computer using the bare option.
git clone --bare https://github.com/contoso/old-contoso-repo.git
cd old-contoso-repo.git
2.Create a target repo.
3.Copy the source repo to the target repo.
git push --mirror https://dev.azure.com/contoso-ltd/MyFirstProject/_git/new-contoso-repo
Please find more detailed information in this document.
In Azure DevOps Import will happen from source repository URL's which are reachable from Azure DevOps Services which are basically running on cloud and require HTTPS reachability.
If BitBucket Server is hosting Repository on Private Network , it will not be reachable from Azure DevOps and hence we need the method provided by Walter above.
When I try to update the environment variables on an Azure DevOps release pipeline, I get the error below.
GitHub Could not create service hooks subscription Unable to configure a service on the selected GitHub repository. GitHub returned the error 'Resource not accessible by integration'.
I am an admin on the GitHub repo.
In Get sources, it is currently configured for a GitHub OAuth Service Connection. Another user is able to update the environment variables. I am using GitHub (not enterprise).
Is this an Azure DevOps permission that I do not have?
Is this an Azure DevOps permission that I do not have?
This error message usually comes with GitHub App installation token service connection.
Go Project Settings => Service Connections to check the details of the specific service connection. If your service connection is GitHub App installation token based service connection, then it's expected behavior to meet that issue. Our team are working on adding that support so far, please check this ticket.
Workaround:
1.Create a new service connection with OAuth/PAT method and use it in your pipeline. Since you're admin of the github repo, a Github PAT is more recommended.
2.If you have permission to the service connections and to the pipeline, this issue won't occur. Ask your Azure Devops project admin to via manage security.
After working with ADO tech support, it was discovered that we needed to remove the artifact and trigger definition from the release pipeline, and then re-add it. It is believed that there was cached service connection, and this updated the pointer to the correct service connection.
I was facing a similar issue when attempting to enable CI for a build and found this article and after digging in deeper I discovered that the issue was the actual PAT we created for the automation. What we missed originally was enabling the admin:repo_hook for the repository. This took longer to uncover than it should have, but just wanted to add that, as removing and re-adding things didn't really do anything for us.
I have created an organization inside GitHub and moved my personal repo to the organization repo. Then I have added service connection with Git and also did GitHub connection inside azure DevOps. Now I would like to access my organization repo from azure build pipeline but it is not listing my organization repo and it only shows personal accounts repos.
It is saying "This setting is required". But I have added git connection and also service connection.
Accepting your help and suggestion.
Please check whether the selected service connection is to a GitHub-InstallationToken. When I choose this type of service connection, I reproduce this problem.
In addition , you can try to create a new service connection authorized with GitHub personal access token to see if this problem still exists.