I have newly started exploring capabilities of Azure DevOps Wiki. I have multiple projects in Azure DevOps. I want to create one separate project to store Business & Technical documentation for all my projects in a centralize place. How can I add multiple Wiki pages to keep this organize.
Second question is I have a predefined structure for the documentation. For eg. Purpose Of Application, Local Build Steps, Deployment Steps, Third Party Control used, etc. How can I create & store this as a template so that whenever a new project documentation is to be created this document can be used as a placeholder to be followed by everyone.
How can I add multiple Wiki pages to keep this organize.
In Azure Devops, Wiki is similar to another kind of Repo. You could Clone Wiki to the target project and Publish the code as wiki.
Here are the steps:
Use the Clone wiki option to get the URL from other projects.
2.Navigate to the target project -> Repos. Use the import repositoryoption to import the wiki to the Repo.
Use the Publish Code as wiki option to publish the repo as wiki page.
Here is a doc about clone wiki.
How can I create & store this as a template?
Azure Devops doesn't support creating wiki templates now.
Here is a suggestion ticket about this feature. You could vote and add comments in this ticket.
Hope this helps.
Related
In below image I can see that there are multiple tabs when we create pull request like Overview, Files, Update, Commits, etc. I want to add a new tab in pull request. I tried searching on internet but was not able to find much. It will be great if someone can help me with it.
Thank you
I agree with #4c74356b41 AFAIK that's not possible without creating a full-blown extension\addon.
Reference taken from :
Azure DevOps-Add extension that adds custom tab to Pipeline / Release Definition page (not the summary page) - Stack Overflow
. I don't know the term I should use to search for it.I am just not sure what to search in google to learn more about it.
you can search for the following terms on Google :
Azure DevOps extension samples
Azure DevOps extension custom tab
Azure Devops Extensions Overview
I am ok with adding addon\extension. I actually want to know some document references that can be useful in this scenario
As you are ok with extension you can refer this MS document Extensions overview.
To create a new tab in a pull request, you need to create an extension that adds the new functionality to Azure DevOps. You can use Visual Studio to create a new Azure DevOps extension project.
Reference for Working with Pull Requests in Visual Studio Code and Azure DevOps
Reference SO thread
From what I’ve read that for each collection will be migrating to one organization. Is there any suggestion or other way to migrate to solve this issue?
By default we cannot achieve that by the official migration tool. Since each collection maps to one database in Azure DevOps Server, and the migration
process works by importing an entire collection. So, each collection will be migrating to one organization separately.
As a workaround, you can try to create new projects in the migrated organization, then manually migrate the projects, of course it will has some limits.
For the sources,you can import the repository directly, please see
Import a Git repo for details.
For work items you can use the third-party tools or extensions or
Microsoft Excel to do that, however the history will be missed. You can reference this thread: Move bugs with history and attachments to a new project
I want to hide two repositories (App 1 and 2 below) from the menu on a project on Azure DevOps.
Select a project -> Repos -> below
The reason is that App 1 and 2 have code, but are not being used at the moment. So we will show them in the future. Thus, we want the ability to show/hide them.
Any idea?
You can go in your azure devops setting to edit your repository settings.
In this page you can manage all security options and allow specific user to work with your branches.
Some documentation from Microsoft website :
https://learn.microsoft.com/en-us/azure/devops/organizations/security/set-git-tfvc-repository-permissions?view=vsts&tabs=new-nav
I found out that you can disable the repository. This will keep listing your disabled repositories but no one can access them. Instead, the repository page just warns about its disabled status (see the picture below).
See this article that brings more detail and is the source of the images below.
I am trying to give a designer access to specific folders within an Azure website I have. I would like for the designer to have access via FTP. However, according to this post, having multiple FTP user accounts on the same Azure website is not possible and the accepted answer suggests coming up with a "different way to manage" the website. This means that if you want collaboration on an Azure website, you have to share the entire directory structure. Please correct me if I am wrong.
I know you can download the Publish Profile settings from Azure as seen on this post. This does not solve the issue as the publish profile simple gives you the FTP credentials for a specific website (instead of all of your Azure websites) but still does not provide the option to create new FTP users with limited directory permissions.
So, my question is: is there some way to edit the Publish Profile settings when they are downloaded so folder access is limited? If not, what methods have you used for website development collaboration on Azure where certain folders should be hidden and protected?
For collaborative work with Azure Websites, you can enable source control. This includes tfs, git, dropbox, bitbucket, and codeplex. Dropbox is not the best collaborative tool, as it's not designed to be a version control system, but it's very convenient.
If you have a repository with any of the abovementioned providers, you can now give your designer their own account with the version control system.
You guys are right about using a source control system like GitHub instead of trying to provide access by creating a second FTP user.
Others have asked this question - not in the context of azure though.
This post talks about using submodules on github to give a contractor access to a subfolder and all folders / files under that sub folder.
SO - I believe linking azure to github would be necessary and then from there, creating and managing submodules from github would allow for collaboration. I believe a required aspect of this would be to have a private repo on github for the main repo. All of the files in the repo would otherwise be available for forking which would defeat the entire purpose of maintaining some discretion on access rights in the first place.
I plan to use two websites in a single web role. Ref: MSDN.
I can do it easily when Web Poject source code. However I need to install Orchard & Magelia (shopping cart) together. They are available as deployment package.
Q.1. Can I wrap deployment package into azure solution?
Q.2. If not, should I download source code of orchard & Magelia then publish? I wonder how other community members are working on this !
Related question here on codeplex.
Copy binary published package via FTP to azure website.