I have an existing Github repo, I want to move it to Azure Devops repo. In github repo, I have some security policies settings. So I have some questions:
Will Azure have these Security policies when I clone the github repo ?
What components beside code, branches, commits, pushes,... will Azure clone (or not clone) when I move Github repo to it ?
Related
I have a repository in GitHub and have a bunch of documentation(.md) files there.
I want to migrate the documentations into one of the Azure DevOps Wikis.
I am referring this link.
When I am using the option Publish code as Wiki,it only shows the repositories which are available inside the Azure DevOps project.
Is there a way I can publish the GitHub documentations in repositories which are from another project into the Azure DevOps Wikis?
Consider approaching this differently. If you are using git for your Azure DevOps project, then the Azure DevOps Wiki should be persisted to a hidden, but locatable, git repository. Git clone the source and target repositories locally. Then copy what you want to the target (Azure DevOps Wiki, local clone). Git add, commit, and push the added target files.
Attached images/files, if any, may be more problematic depending on how exactly they are represented in the source GitHub repo. In Azure DevOps Wiki ALL attachments are simply stored in a root .attachments folder. So, you'll need to migrate them there and "fix up" your links.
I've done this going the other direction, Azure DevOps Wiki -> GitHub Enterprise repo. You should know that you’ll likely need to “fix up” page links and that the two markdown styles have slight variations you may have to address.
Is there a way I can publish the GitHub documentations into the Azure DevOps Wikis?
for copying documents from GitHub you need to use Import repository from your devops project.
how to import an existing Git repo from GitHub, Bitbucket, GitLab, or other location into a new or empty existing repo in your Azure DevOps project.
For complete information you can go through the Import Git repo link.
Boss wants me to set up a pipeline in Azure Devops to our Gitlab repos. I have a few questions:
Do I set it up under "Git other"? Should I mirror the repositories into Azure Devops?
I am supposed to set it up with a docker image, do I need to use docker hub?
I've never set up a pipeline and I am just a lost intern, thanks for any advice.
Do I set it up under "Git other"?
Yes, you could use the Git other to create a Service connections for the
GitLab. And there is an extension GitLab Integration for Azure Pipelines,
which could be able to download the sources from a GitLab repository (using
clone command) and use downloaded sources in Azure Pipelines.
Should I mirror the repositories into Azure Devops?
If you have no plans to migrate gitlab repo to azure devops repo, you do not need to mirror the repositories into Azure Devops. Besides, just as LJ said, since the YAML structure does not support for Gitlab at this moment, we could not use YAML structure with Gitlab repo.
I am supposed to set it up with a docker image, do I need to use
docker hub?
This is a matter of taste. In addition to dikcer hub, you can also use Azure Container Registry.
Do I set it up under "Git other"? Should I mirror the repositories into Azure Devops?
If you want to set up the pipeline using the YAML structure and have all the features that Azure DevOps provides, you have to mirror the repository since it's not possible yet to use the YAML file to run pipelines directly from GitLab and Git other connection has some limitations.
I am supposed to set it up with a docker image, do I need to use docker hub?
For the pipeline environment, you can use VM Images provided by Azure.
While creating a project in Azure DevOps , the repository connection to the GitHub has been pointed.
But if you push any code the GitHub repository, this update is not seen from the Azure DevOps Reps view.
Even the creation of the new branches at GitHub site are not shown in Azure DevOps.
This is because it doesn't do what you think it does. Connection is not supposed to sync content across repositories. Its "just" being used to connect to the repository on the build agent and pull the sources. If you want to sync repos in Github and Azure Repos you'd need to implement a custom solution. Nothing built-in exists in Azure Repos or Github.
https://learn.microsoft.com/en-us/azure/devops/boards/github/connect-to-github?view=azure-devops
In my Azure repo for my function app, I included a submodule that is cloned from another Azure Repos. I try to enable CI/CD pipeline of this function, however, if I change and commit a new change to the submodule's original Azure repo, it cannot trigger a new build and deploy of the function APP. Is there a way to enable CI/CD for Azure repo submodule change?
For this issue, you need to enable the Checkout Submodules option in the advanced section of the Get Sources step.
You can refer to this document for details.
I'm deploying with Visual Studio Team services to Azure (NodeJS) but the problem is when files are changed in the remote repo in azure (through my site) I can't get them to my local repo. How can I get it without manually going in and copy the files? (Git pull doesn't work)
According to your description, I assume that your local repository is link to VSTS repo and VSTS repo push files to Azure Remote Repo. In this scenario, your local repo isn't linked to Azure Remote Repo, when you execute git pull from local repo, it just try to pull the changes from VSTS repo, not Azure Repo. To pull the changes from Azure Repo, trying the steps blow:
Configure "Deployment credentials" from Azure Portal. You'll need to use this credential to authenticate Azure Repo.
Open Kudu service page of your webapp. For example, if your app url is "https://app1.azurewebsites.net/", then the Kudu service page is "https://app1.scm.azurewebsites.net/".
Click "Source control info" link in Kudu service page. You will get the URL of the Azure Remote Repository.
Go to your local repo and add a remote repo with the URL you get from Step 3.
Perform a pull action from the new added remote repo and enter the credential you configured in Step 1 when prompted.