We're using TFS 2017 for our CI/CD and I'm trying to configure the users for the Approvals on the production Environment definition of a Release definition.
What I'm try to achieve is assigning two groups of users as approvers, one member of each being required to sign off the release. The screens suggest this should be possible but it's proving difficult to configure.
I've created a Project Manager group and an Infrastructure Team group, both at a TFS collection level and at the project level within TFS and assigned the appropriate members.
Having created the Release definition and created a production Environment, I select the Assign Approvers... which displays a new window. I select the
Pre-deployment approver | Specific Users option, click the More Options link and select the All users in any order option.
However, when I try to select the groups, it doesn't show me any of the groups I've created and I can't select them.
I know that I should be able to manage this via AD but I don't want to have to keep getting AD groups made for me if I can manage this myself within TFS.
Has anyone managed to achieve this in TFS 2017 and could you tell me how please?
I can create the Groups in both Collection and Project level and can select them to Release Approval. Everything works correctly.
Please note that the Groups will not display automatically, you need to enter the Group name in the Search user and groups text box to filter it out. Just have try for that.
Related
I added a user to Team Foundation Server DevOps, but when the user entered the URL made a mistake, he entered an URL that does not exist.
I tried to remove this broken address, but does not let me delete it, there is no way to delete it in the graphical interface of Visual Studio, I tried to correct eliminating the cache of Team Foundation, I have tried to remove the workspaces, but it does not manage to eliminate this broken URL.
I have also tried to modify this URL that is misspelled but when editing the workspace, will not let me modify that address.
Here is a screenshot of the URL I want to delete, when I delete a workspace and click on Update or simply add the server to which the new user has permission to access for some reason the broken URL is not deleted, it seems that when you click on the download button and assign the existing server files if it appears as if you downloaded the solution's files but when checking in the file explorer there is nothing, and the broken URL is still there by default, I send a screenshot so you can view the problem, you will not find the local path where the files are saved because the entire Team Foundation Server cache is reset.
The broken URL
Ok, I found the solution, it turns out it was very simple, the problem was that when you add the user to the project by default is added to the stakeholder level, and that level does not allow changes in the source code, only at the administrative level, such as assigning Tasks, view assigned tasks, etc...
At the time of wanting to change the level within the project in the Web portal does not allow it to do because the change must be made at the organization level, so it is only necessary to enter the portal of the Organization then:
Click on Organization Settings--> Users--> Change access level (click on 3 dots in name of user) --> Change from Stakeholder to Basic
Ready... Problem fixed!
I'll add some screenshots of the process:
Click Organization Settings
Click on Users
Change access level
Change Stakeholder to Basic
Working with TFS 2010 Power Tools, and able to edit template Fields via Process Editor.
However the Fields tab in the editor does not show "all" fields in that Project Collection.
For example if you create a field CompanyName.FooField in Team-Project-A, you will not see it when opening the Process Editor for Team-Project-B within the same collection.
Yet, you are not allowed to create a new field with the same Name or RefName. TFS insists on Name & RefName to be unique in the Project Collection.
You are allowed to create a New field in Team-Project-B using the same Name & RefName for FooField - I'm assuming field is somehow re-used across 2 Team-Projects.
After doing some research, TFS allows for fields to be re-used as long as they are within the same Project Collection (can be in dif. team projects).
Work Item Field Explorer (Tools/ProcessEditor) shows a READ-ONLY view of all fields.
Its obvious that TFS maintains a "Global" Field definition on the Project Collection Level, yet there seem to be additional association with individual Team Project.
It would be extremely helpful if there was a similar way to EDIT all fields at once within a Project Collection as opposed to bouncing between Process Editor windows for each Team Project.
Is there anyway to do that or has anyone faced a similar problem?
It is impossible because two collection projects are necessarily created on two different data bases, so the difficulty of achieving what you want, but betweentwo projects it is possible because they are on the same database instance.
link : http://msdn.microsoft.com/en-us/library/vstudio/dd236915.aspx
I have a solution with 5 Azure roles and the Azure solution is set as the startup project. When I run the solution 5 internet explorer windows popup, 1 for each role. I want to only run the role on which I'm working.
If I comment out the roles in the servicedefinition.csdef file VS2010 complains when the roles are referenced from within the various .cscfg files.
If I comment out the role in the currently executing .cscfg file, VS2010 complains about the reference from within the .csdef file.
Right clicking the Azure project and selecting Manage Roles does not allow me to select which roles are actually executed.
What's the best way of disabling roles that I'm not interested in?
The easiest way I can think of is to just disable the endpoint starting up in the browser.
Right click the role under the Azure project - properties and scroll down to:
And uncheck the endpoint for the roles you're not currently busy with.
I asked this question originally on ServerFault.com, but there seems to me more activity regarding TFS 2010 on StackOverflow.com, so I decided to re post it here...
It is my understanding that "Project Collection Valid Users" TFS group can no longer be modified directly.
However, I would like to grant all of my domain users (Windows group called "DOMAIN\Domain Users") a "reader" level access to TFS project Collection...
I know I can go to each Project and add "DOMAIN\Domain Users" to [Project]\Readers group but I am wondering if this is possible to achieve in "one shot" so that future projects are already accessible when set up.
To have this AD group added to a TFS group for your upcoming projects you have to modify your project template. There you can preconfigure your projects, exspecially set permissions to groups and users.
For the existing projects you have to do it by hand. I don't know any other way than that.
My approach is based on the fact that TFS permissions are inherited unless explicitly denied.
To create an user group that will automatically access with read only permissions to all existent projects as well as the futures ones, follow those steps:
Create a new security group at the project collection level. You can do it in Visual Studio using the "Team/Team Project Collection Settings/Group Membership" menu.
Add the new group as a member of the "Project Collection Administrators" group. This will grant access to all projects in the collection, including the futures ones.
Limit the permissions of the new group to remove the administrator permissions inherited. To force the read only access, Deny all permisisons except "Create a workspace", "View build resources" and "View collection-level information".
The users of this group will have read access to source code, work items, and build definitions of all projects in the collection.
We have three servers for each mode:
Development
Testing
Production
Each one of them has different settings for connecting to the database, different base paths for resource accessing etc.
How do I create different debug and release modes for each of those server types and how do I force them to use a different configuration file?
Is there an easy way to switch between them?
Right-click on project->properties->Configuration Manager.
To create solution profile("configuration"):
Click drop-down "Active Solution profiles", select edit.
To create project profile("configuration"):
In "project contexts" "grid", click on dropdown from "Configuration" column, select edit.
To select project profile for solution profile:
Select active solution configuration, then select desired project configurations for each project.
Each profile can have different settings - i.e. target path, include directories, etc, etc - basically everything you can set on property pages can be different for each profile.
They will use same file though.