I'm using tfs to save a project inside "My Organizations" in Azure DevOps.
I've succeded, now I can commit my project.
During this process I left some "corpses" and I have no idea on how get ride of them.
I cannot delete them inside VS and if I enter on "My Organizations" only the working project is visible.
Why this repos aren't visibile on My Organizations list ?
Related
https://learn.microsoft.com/en-us/azure/devops/repos/tfvc/branching-strategies-with-tfvc?view=azure-devops
I have a brand new project in Azure DevOps. There's nothing in it yet, but I want to set up the branches to model the Servicing, Hotfix, Release isolation strategy from the link above.
To do this, I need a branch, and a branch of a branch.
When I right click my project and say "Branch", it prompts for a Target.
This is where everything I try does not work.
First thing I tried was to use $/Master/HotFix. This returns an error "The target item $/Master/HotFix cannot be under the source item $/Master.
Then, I tried just $/Master-HotFix and get an error "Source control must branch into an existing team project. Master-HotFix is not a team project"
So, I went to Azure DevOps and I created a new project called Master-HotFix. I mapped it in Visual Studio, and tried again. This time, I got the error "Unsupported pending change attempted on team project folder $/Master-HotFix. Use the Project Creation Wizard in Team Explorer to create a project.
Surely making a branch isn't this difficult? What am I missing?
According to your description, seems you get promoted a kind of below dialog
I have a brand new project in Azure DevOps. There's nothing in it yet
You are trying to branch a Team Project rather than a folder containing your code.
You should first have your code in a folder, say "Master", under the "$/TeamProject/" folder. You can then branch "$/TeamProject/Master" to "$/TeamProject/Master/child".
If you have dumped all of your code into the root of your team project then you will need to move it into a folder first, then branch that folder.
warning: You can create a new team project that is a branch of this one, giving you "$/Master". However this method is a terrible idea and will lead to pain and suffering
For more details please refer our official tutorial:
Convert a Folder to a Branch
Branch a folder or file
In order to branch in TFVC you first need to create you master/MAIN branch as a folder. Then you check that folder in. After you can convert it to a branch from the branch menu. After that you'll be able to branch off that master/MAIN branch and create the structure you are trying to do.
Cheers,
ET
In Visual Studio 2017, How do you connect to a TFVC project in TFS and prevent it from creating a local repo? I want to be able to copy files from another project in VS 2017 and check-in but not have all the files from that project local?
In the source control explorer, drill down to the project folder you want to add the files to, right click on the folder (you don't have to have it checked out) and click "Add items to Folder".
You should see an "Add to source control" dialog that is showing files from your local computer. From there, it's not too hard to follow.
When you connect to a TFVC project in TFS you could select to create local workspace or not. But we could not restrict users to create local repo or not.
If you do not want others to pull files from server to local, you need to use permissions to do the restriction.
You could directly copy files from another project to your local workspace, VS will auto detect changes and list in the pending change list. You just need to check in files.
More ways about how to add files to the server, please review this official tutorial.
For some reason my build definition are not working properly if long path mappings. If I were using the path $/Project/Samples it works OK.
My build has this in the repository tab:
Then the logs show that there is no SLN found, and I confirmed that nothing was downloaded to the agent working folders:
For me it's a bug when getting sources, as I can't see a good why it is not getting correctly the files. I already tried to add files in some folders above and it works. Some ideas?
This permissions issue must be addressed at both the Team Project Collection and Team Project scopes.
First, the Team Project Collection:
Browse to http://[my_tfs_server]:8080/tfs/[my_collection_name]/_admin/_security?_a=members (your Collection's Security admin tab)
Click on the TFS group "Project Collection Build Service Accounts"
Ensure the user (not group) "Project Collection Build Service (TEAM FOUNDATION)" is a member of the group
If it is not a member, add it with the "Add Windows user or group" menu, then Browse -- you should find it in the list of users
Second, the Team Project:
Browse to http://[my_tfs_server]:8080/tfs/[my_collection_name]/[my_team_project]/_admin/_versioncontrol
Ensure the user (not group) "Project Build Service (TEAM FOUNDATION)" is present in the security list (along with the "Project Collection Build Service Accounts" group)
If it is not a member, add it with the "Add Windows identity" menu, then Browse -- you should find it in the list of users
Third, ensure that the "Project Collection Build Service Accounts" group and "Project Build Service (TEAM FOUNDATION)" user have appropriate version control rights, such as Read and Label. Make sure that Inheritance is set to On.
With these permissions in place, the -1 issue should resolve.
"workspace version -1" usually occurs when there is no permission to access to the source control. Check the "Inheritance" settings for the folders in your source control and make sure it is set to "On". Refer to this link for details: TFS 2015 Build Agent failing syncing the repository.
Similar question here: TFS 2015 build agent failing to sync TFVC.
This maybe a long path error. A way to fix this issue is to reset the workfolder path.
The default work folder location is a _work folder directly under the
agent installation directory. You can change the location to be
outside of the agent installation directory, for example:
/WorkFolder:C:_work. One reason you may want to do this is to avoid
"path too long" issues on the file system.
Source link
And also set Clean = "false". This may also be the root cause. If you have set /Project/Samples and build the definition. It will pull down all files under /project/Samples. Set the long path again, there has been files in the working folder. TFS may not get the new files. Set Clean= "True" and try it again.
We have a development server that is running TFS 2010, it is working fine however we have a bit of issue:
when person X take the latest and build the app , it get checkout abc.csproj application and due to that another person can't take the latest and it shows the error message as.
Here I'm looking for, whenever we modify any changes locally (pages) it should not get checked out & lock by TFS, only in their local repository it changes.
any suggestion would be appreciated.
There are two places you may need to change TFS to allow multiple check-outs.
In Visual Studio, use the "Team" menu, then "Team Project Settings", then "Source Control..." and ensure "Enable multiple check-out" is checked.
In Visual Studio, use the "Team" menu, then "Team Project Collection Settings", then "Source Control..." and ensure that if "csproj" is listed there, it has "File Merging" set to "Enabled".
I want to use a free tfs account for a sample project. So i created a free account on visualstudio.com and created 2 collections. And i want delete one them but i cannot delete it.
There is no any members in the collection. It doesn't allow me to delete. As you see on the screenshot, delete button is disabled. Also Is there any way that if i've an admin account, is possible to change or delete collections from visual studio?
I'm not sure how/if it applies to free TFS versions, but the following link shows how to delete Team Project Collections in general. Looks like doing it via command line tool is the way to go.
https://rules.ssw.com.au/do-you-know-how-to-delete-a-team-project-collection
Here is the main part:
On TFS server, open Administrative Command Prompt and change to TFS Tools Directory.
%programfiles%\microsoft team foundation server[versionnumber]\tools
Type the command:
TFSConfig Collection /delete /collectionName:[COLLECTION NAME]
You're mixing collections and team projects. You cannot create a collection in Team Foundation Service as of now. That may or may not change in the future. When you sign up, there is one collection created for you and that one will contain your team projects and you will need to live with that one. If you have a need to have another collection then you can sign up under another account. You can however delete team projects but not from the web UI. You will need to use the command line tool DaveShaw gave a link for. You can also check out the blog post below:
How to delete a team project from Team Foundation Service (tfs.visualstudio.com)
You look like you are trying to deleted a "Team" from a "Team Project"? You have to have at least one "Team" in a "Team Project", and that will have the same name as the "Team Project".
If you are wanting to delete the entire "Team Project" (containing all the Work Items, Source, Builds, etc), you can do it using the tfsdeleteproject command line tool.
Even we had similar issue. Unfortunately we had deleted a Collection DB without Stopping and Detaching the collection from TFS admin console in TFS 2018. Later we tried to detach the collection, but no luck. Initially we had ignored this issue since it was test TFS collection and that too in QA server. Later during up-gradation to Azure DevOps 2019 server we faced issue with Existing Deployment option. we couldn't complete the upgradation. we followed below steps to fix the issue:
**1. Restored the VM/QA TFS server with VM snapshot backup created before upgradation.
Run below command to remove the deleted collection from TFS Config DB.
"TFSConfig Collection /delete /collectionName:[COLLECTION NAME]"
Stop TFS services and done upgradation to Azure DevOps Server 2019 successfully.**