I am setting up some solutions/projects for my small team here however the solution/project build configurations don't seem to go into TFS.
When we download the solution on another computer? They are empty.
Also, sometimes on the same computer, they just disappear alltogether?
Any ideas how to add this into source control? When I change them, there doesn't appear to be any pending files in the solution to check into source control.
The build configuration information is saved in the solution file. When you add/update the configuration from "Configuration Manager", the solution file will be updated accordingly and the changes will be displayed in "Pending Changes". Check in the pending changes will sync the configuration update to Source Control. Following is a screenshot for configuration change:
Related
I have an Azure Web application that I checked into TFS yesterday with no issues. Upon checking in, the resource manager will inject our nuget packages and deploy if it builds successfully.
I made a few changes (added a class) and checked in today. I received this error on the build:
Here's the quote to help the future search bots:
Exit code 1 returned from process: file name 'tf', arguments 'vc unshelve Gated_xxxxxx;****** /loginType:OAuth /login:.,******** /noprompt'.
I looked into the log response, to see if I get more detail, but it says the exact same thing. I have not changed my password or username.
How can I debug this to figure out the issue?
UPDATE
To save others from the headache. The issue was that we had CI builds per project. A file from another project had snuck in as well. So I was checking in for 2 different projects on 2 different solutions (Which both go to the same TFS server). So make sure you only check in for that one project!
To save others from the headache. The issue was that we had CI builds per project. A file from another project had snuck in as well. So I was checking in for 2 different projects on 2 different solutions (Which both go to the same TFS server). So make sure you only check in for that one project!
You can receive that error as well if you try to check in a file that is in a project that is not mapped in your build definition.
Let's say that you have a file named FileA.cs that is in a project named ProjectA.csproj. If you do changes in FileA.cs and this file is included in your changes, you need to map ProjectA.csproj in the Get source step of the build definition.
I have an unusual situation. On TFS 2013 build environment, shelveset builds fail when the users shelveset contains added/new files.
The user creates a shelveset with the news files added and some
changes to existing files.
User queues a build with the shelveset.
The build server creates a new workspace, merges the shelveset files
and the added/new files all have "Warning: There are other pending
changes against the item." in the build log.
How do I fix this?
We ran into this a lot when we were in TFS 2013. They seem to have fixed the issue in 2015 which doesn't help you now.
I seem to recall that we could work around the issue by shelving without preserving changes in the local workspace so that there aren't conflicting pending changes from TFS's point of view. You could restore the files to the local workspace by unshelving them after the build completes.
How do you exclude a project from the solution that is built by TFS?
I have:
Created a configuration and unticked build for the project I want to exclude.
Checked in the changes to the sln from above file to TFS.
Triggered a build under TFS with the build configuration I have added.
This doesn't work. When I build locally I can see that the build skips the project (I get "Project not selected to build for this solution configuration"). When I look at the TFS build log, I can confirm that the same configuration is used, and that the project gets built.
Looks like some sort of bug. Had the same issue.
I resolved it by manually removing the offending project from the solution file.
Find the project's GUID in the solution file - note it is the last GUID on the line, the first one seems to be the solution GUID.
Then find this project GUID and the various configurations for it in the GlobalSection(ProjectConfigurationPlatforms) section of the solution file and remove the ones you want.
Not ideal, but it works.
I have been working with a TFS project that supports copying build output to source control. If I open the build definition, this is under "Build Defaults". There is an option to copy build output to a source control folder.
I have just installed TFS Server 2013 (with update 2) and I want to use this feature with a new Team Project. However, if I create new build in VS 2012 or VS 2013 on the new server, I am not given the option to copy build output to source control. What gives?
I am not looking for a workaround, I want to know what to change so that my server acts like the first one I described. Thanks!
Screenshots of what I'm talking about: http://imgur.com/a/mhDNQ
This was a feature that was temporarily present in TFS, but I believe has since been removed. If I recall it was put in there specifically to support the cloud-hosted elastic build servers which didn't have access to network shares to drop the builds in.
Most people recommend against putting your build outputs into TFS. The best approach is to publish them to a NuGet feed.
In any case if you want to put your build outputs into TFS (or a NuGet feed) you'll have to modify the build workflow to do that yourself.
Open a new build definition > process.
Under template select new and you should be able to choose project and folder. Find your original template and link it. Your option should appear.
In TFS 2013 this has changed to be "store drops in TFS". When you select this option the drop I'd stored in a new inversioned store that you can access.
While you can easily get the files out as indecision or zips the built in tools like release management do not support it yet. I would recommend that you use this option but publish your assets to a nugget repository.
If your TFS is available online (VSO or https) then you can use MyGet to dynamically load the nugget packages that you are publish and make them available on a feed.
http://docs.myget.org/docs/how-to/use-tfs-online-git-with-myget-build-services
I didn't get any overlay change when my teammates make changes or add a new file to my project.
Should I regularly update my project to keep track with the updates made? Or am I missing any configuration part that shows a new overlay whenever any of my teammates makes a change?
Note: I get red and other overlays correctly whenever I make changes to files.
Yes, you would need to do periodic updates to get changes from you team members. The trigger for this could also be one of the folloiwng.
A notification from the continuous integration when a build containing changes from other team members has been done.
A post-commit hook in your subversion server which emails all interested parties whenever there is a check-in.