I am used to working with Perforce and I really like the ability to be able to group checked out files under different pending changelists. For example, if I am working on two bugs at the same time and the changes made for them can be grouped separately.
I am unable to find this functionality in TFS. Is this supported? If no, what is the best practice around it?
I am using VS 2015 Professional with TFS Server 2015.
No, it's not supported with pending changelists in TFS for now.
To be a workaround, this is possible using the Suspend/Resume feature in Visual Studio 2012 and above. It will allow you to keep multiple shelvesets, associated to multiple workitems. Only problem is that you can't have all two bugs open at the same time, so you'll have to check them in one by one.
More detail info please refer this link: Suspend your work and manage your shelvesets
Related
We have 2 TFS servers, one is inside the firewall, and the other one is outside the firewall. Because of security reasons, we still need to keep it this way. But the question is: is there a way to Sync these 2 TFS servers, say at every night?
Say we have servers TFS1 and TFS2, right now, we only want to Sync from TFS1 to TFS2, not bidirectional synchronization. If possible, we want to have complete synchronization.
I searched some time, but I could not find a good solution. It seems all recommendations are for old version TFS.
Are there any solutions for the latest TFS? existing products? Or, some information about API that we can use to make a tool for this?
Thanks
There is nothing changed with sync two TFS servers for the latest TFS version. Just as Daniel and many other expert suggested:
TFS generally lives in 1 instance and 1 only. TFS is a production
environment for the development team. It doesn't make sense to have
two TFS systems and have them synchronize to make this separation.
Having your teams work on two different TFS environments at the same
time is a very strange requirement.
Source Link
The best solution in your case, negotiating with your IT team, set up a safe and stable way to allow your top Management users to connect the internal TFS. You could also set up SSL for your TFS server to improve the safety.
It will also save you a lot of time costs for maintaining two servers syncing.
If you insist on syncing two TFS servers take a look at this similar question: Sychronising work between two TFS servers
Another way is using VSTS instead of your external TFS. Microsoft has documentation on this exact scenario which can be found here: Migrate to Visual Studio Team Services : Move from Team Foundation Server (TFS) to Visual Studio Team Services (VSTS) and bring your data along.
This link also contains the download link for the migration tooling which you will want to use
Currently the following versions of TFS are supported for import:
TFS 2017 Update 3
TFS 2018
TFS 2018 Update 1
My development team is using TFS for source control. My current plan is to have a new shared branch created each sprint for the developers to use for all their tasks.
What is the best way to ensure that the developers are performing forward and reverse integration every day for that branch? In other words, how do I make sure they are constantly getting the latest code set from the sprint branch and checking their code in as well?
There is no such VS extension can force developers to get code from TFS and check in frequently and continuously.
If which you want is to "get the latest " and avoid TFS force you/colleagues to resolve conflicts before checking in.
However, TFS redefined what "Get Latest" does. In TFS terms, Get Latest means get the latest version of the files, but ignore the ones that the server thinks is already in your workspace. Moreover, doing a get latest is good practice, but not mandatory. There is no such settings.
There has been some similar questions in SO and got an amazing answer, below links for your reference:
Is performing a Get Latest mandatory before checking in in TFS so you do not overwrite/lose code?
Why doesn't TFS get latest get the latest?
As a workaround, if you really need this feature in your team, you could set up a reminder such as meeting reminder in outlook 4:00PM to remind your colleagues, they should merge their work in the branch at the end of day. Just couldn't force them to do this.
This is a people problem, not a tooling problem. There's no way the tool can force their behavior when it comes to committing their code or merging branches. It's just part of workflow discipline, which will come with time.
I am using TFS Service (on the cloud solution) and I would like to customize the bug states.
There are many resources explaining how to do that using TFS Power Tools, so I downloaded and installed it.
I am able to open the workflow, but I am not able to change anything because I get the following error message:
Failed to save the 'Bug' Work Item Type to the server. TF237113: You
don't have enough permission to complete the import operation
I am using an administrator user.
Is it possible to make this change on Visual Studio Online?
While you are correct that it is not possible to customise the process template on Visual Studio Online you do have a few options:
Kanban Columns - If you want to you can customise the Kanban columns so that you have 'meta states' that you can use. I know that it is not the same but it could get you there.
Go offline - Currently and for a limited time you can take your VSO account on-premises. The TFS team are holding the version of VSO in parity with TFS 2013 Update 2 so that folks can do this. Be aware of what you loose though. No frequent updates and you have to host your own servers...
Not sure if these options help but they are options...
Making more research I found the answer: it is not possible:
http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3654231-customize-process-template-on-visual-studio-online
We have upgraded our TFS from 2010 to 2013, and the same time moved the TFS and databases to new servers, with new names.
One of the very few annoying effects (Probably due to moving the TFS to a server with a new name) is that the build controller/agent from the old server is still visible in lists of available build controllers/agents, but is not visible in the admin gui for build configurations and therefore not possible to remove.
Does anyone have had the same experience and furthermore have a solution of how to remove the traces of old (and not used/wanted) build controllers/agents?
Kind regards,
J
Ok.
Sorry, I found the solution myself now after continue searching and yet again scanning through the microsofts documentation! :)
It's possible to disable and delete controllers and agents through the Manage Build Controllers in Visual Studio.
Also described here: http://msdn.microsoft.com/en-us/library/ee330987.aspx
Just make sure there is no builds in progress, but that's ofcourse also possible to handle through Manage Queues in Visual Studio.
I'd like to know if it's possible (and how, if anyone has ever done it before) to have Mantis Bug Tracker "tickets" automatically imported/transformed into TFS work items.
We use mantis to keep track of development and TFS as a Repo. Every check-in made to TFS must be associated with one work item. Right now, these two systems are not integrated which causes, for example, that the ticket 100 is relative to the work item 497 without no way of knowing that one is relative to the other.
I've looked at TFS Integration Tools but was unable to install it for some reason at this time.
So, how can I have an automation process that "imports" Mantis tickets into TFS work items automatically? Is this even possible?
There is a plugin for source integration which supports Git, SVN and Mercurial (experimental).
https://github.com/mantisbt-plugins/source-integration
I am not aware that there is something similar avalaible for TFS, but it should be no big problem to implement TFS integration based on the framework which is offered by the plugin.