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.
Related
I have a Azure DevOps Git repo on which two teams are currently working.
We created separate folders under 'feature/' for each team. Can we hide team1's feature folder from team-2?
Using git tf permission command, I was able to restrict the contributory access to other team's folders. But I just don't want the feature team folder visible to other team members.
Please click here to view my branch folder structure
As per the image, team-1 members should be able to see only 'feature/team-1/' branches. 'feature/team-2/' should not be visible to team-1 people.
It's NOT supported to hide specific branch for other team in Azure DevOps UI.
It's only supported to hide specific repo for one team, but cannot for branch level.
Azure boards MS Team integration. Only showing Issues or Epics, where are my work items?
I added a tab into a Team channel, and I can see Issues, but there is not option for showing the Work Item field?
On the Azure Boards website I see both fields: Issues and Work items.
Here is no Work Item field
This is the website showing both types at once
As I understand, you are not able to see work item field.
If you need to see work item field,
you need to connect to a project and not just a repository.
From the connect to a Project dialog.
Use CTRL-Shift to select your options and then choose Connect.
The new Work Items experience is available when you connect to a Azure Repos Git repository.
For further reading please follow the document.
You need to set up and manage subscriptions for creating and updating work items. You can create subscriptions to monitor work items at any time using the #azure boards subscriptions command.
Please go through the documentation for more info.
wow I can believe after almost a year nobody replied you. You can set it up in the Organization Settings > Boards > Settings then you can see the process selected. e.g Agile, Basic (what you mentioned) Scrum, etc.
I hope helped someone after this.
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.
In the gitlab documentation, it reads
Transferring an existing project into a group
You can transfer an existing project into a group you own from the project settings page.
First scroll down to the 'Dangerous settings' and click 'Show them to me'.
Now you can pick any of the groups you manage as the new namespace for the group.
But I cannot even manage to find the settings page.
In the docs there is the following figure:
However, my sidebar looks as follows:
What's going on?
hoping someone has seen this before.
When I try to enable continuous integration in Visual Studio, using Visual Studio Team Services, I get the following error:
"This version control host is unsupported. Repositories must be hosted on VSTS or GigHub." This error gets zero results in google.
As you can see in the screenshot, the solution IS hosted by VSTS.
Explaining the screen shot:
Section 1 in the pic is the pop-up that appears after clicking 'Configure Continuous Integration' in the VS2017 status bar.
Section 2 is my VS team explorer window.
The grey boxes are the company website 'mycompany'.
Additional facts:
The VSTS account is owned by admin#mycompany.com, but my dev account, jason#quantumland.com, has full contributor permissions to the project. I get the same error whether red box 1 above has my personal account selected or admin#mycompany.com
The current loaded solution is the basic starter '.NET Core Web application' in VS2017 Community edition. No authentication selected, no changes to the auto-generated code.
I can build and run the solution locally, check in the solution to VSTS, see the code in the VSTS repository, publish to Azure web app, etc. Everything seems to be working but this.
Appreciate any help. My best guess is that my security permissions are wrong in VSTS, but both accounts are members of the 'admin team' group, and admin#mycompany.com is the creator/owner of the VSTS account and repository, so I don't see how.
You are using TFVC version control, the continuous delivery is used for Git version control, so you need to add a new git repository (can be in TFVC team project: Use Git and TFVC repos in the same team project), and use this git repository as source control.
Article about TFVC and Git: Choosing the right version control for your project
I was able to use TFVC for version control and get CI/CD to work. Following the newer instructions provided by #starain-MSFT:
Continuous Integration
This sets up CI/CD using the VSTS web portal exclusively. It works, but if I click 'configure continuous delivery' in the VS2017 status bar and use that form, I continue to get the error above.
If anyone posts an answer that fixes the exact question asked I'll update and mark that as the answer. Good news is that you can indeed use TFVC with CI/CD. yay, and thanks to #starain-MSFT for the updated link.