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?
Related
I have a new Azure Data Factory.
I have an Azure DevOps organisation. It is connected to the Azure Active Directory I'm logged into when configuring the data factory. I've checked this from Organization Settings\Azure Active Directory of the the Azure Devops website.
I'm trying to configure source control from the Data Factory Studio to a project within DevOps. I've checked that my user account is a "Project administrator" on that project.
From Data Factory Studio, I click the toolbox icon on the left menu. I click "Git configuration" under "Source control"
I'm then presented with a "Configure a repository" window. There are 3 drop-down boxes. I am able to select from the "Devops organization name" and "Project name" but "Repository name" is blank.
I know the target project has a git repo. I am able to clone it from the command line using the same account for which I'm logged into Data Factory Studio.
If I select the "Use repository link" radio button I'm prompted to enter the "Azure Devops link". When I paste this in I get the following error:
I found the answer here: How to resolve no access in Azure Data Factory 2 to Azure DevOps Repository
Needed to upgrade my "Stakeholder" devops account
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
I am planning to use Azure Devops for code repository. I was able to add code to Git repository as you can see in below screenshot (I have a master branch). I am trying to push this to Azure Devops but while click on sync from Team Explorer, I am not able to see those three options:
Publish to GitHub
Push to Azure Devops service
Push to Remote Repository
Am I missing something? I really need to push this git repo to Azure Devops. I have already created a project in Azure Devops to push into that. Please help.
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.
Using the portal:
Using the portal at https://manage.windowsazure.com/ this is easy. From a newly created azure web site:
Go to the dashboard
On the quick glance options on the right, click "Set up deployment from source control"
On the "where is your source code?" option, select Github
Authorize, then choose the repo name and branch.
BINGO: now pushes to that branch will trigger a deployment of that branch onto the azure website. Lovely.
Here's the problem:
I cannot for the life of me see how to do this from the command line (using the xpat-cli installed using npm: "npm install azure-cli -g")
It seems like I should be typing something like:
azure site deployment github --verbose --githubusername [username] --githubrepository [username/reponame] [sitename]
Because the help for "azure site deployment github" says it will: "Link a website to a github account for deployment"
Doesn't seem to work though...
If I then type:
azure site show [sitename]
The output says the source control is "LocalGit" instead of github - which is what it says if I do it the portal way above.
Source Control
data: --------------
data: Type: LocalGit
Any ideas?
Depending on your use case the solution will be different.
Assuming you have the same github source but want to deploy to multiple different Azure websites
Potential Solution: Make use of the Deploy to Azure Button See details here: https://azure.microsoft.com/blog/2014/11/13/deploy-to-azure-button-for-azure-websites-2/
Assuming you have various repositories that you want to deploy to Azure: Potential Solution: I am assuming that you will be the person deploying it. The workflow will be as follows:
A. Download files from Github to local folder See here
B. Publish your local folder into a new/existing Azure site. See here, or here. There are other github repositories to get some scripts right away
I understand this doesnt directly hook your system to do direct pull, but its one way to do it.
There is also:
http://www.imtraum.com/blog/streamline-git-with-powershell/
https://gallery.technet.microsoft.com/scriptcenter/a-GitHub-Repository-265c0b49
Both documents I found describing how to set up continuous deployment from GitHub say that you can configure the repo and branch with an Azure Resource Manager template, but you have to enter your credentials and complete the authorization process in the portal.
The script used in this tutorial will automatically configure
continuous publishing from your GitHub repository. This requires that
your GitHub credentials are already stored in Azure, otherwise the
scripted deployment will fail when attempting to configure source
control settings for the web apps.
To store your GitHub credentials in Azure, create a web app in the
Azure preview portal and configure GitHub deployment. You only need to
do this once.
I'd also suggest posting your xpat-cli problem as an issue on their GitHub repo.