Is there any UPDATED guides to how to do this? I can only find stuff from 2010 which DOES NOT WORK with 2013.
I'm trying to set up a build so when it's ran it automatically publishes the clickonce application. I did find this article, and it was SOMEWHAT working (http://publicvoidlife.blogspot.com/2014/05/continuous-integration-with-tfs-and.html), but I could not for the life of me get the version updating part working, so I scrapped it.
I'm currently using the default TfvcTemplate.12.xaml and I really don't know how it fully works. I'm a novice here and could use a nudge into the right direction.
Here's a guide published 4 days ago...
Build and Publish a ClickOnce App using Team Build/VSO
http://blogs.msdn.com/b/tfssetup/archive/2015/09/15/build-and-publish-a-clickonce-app-using-team-build-vso.aspx
Related
We have a requirement of associating work items with TFS Builds. Generally, this is possible (or we can say 'natural') while using XAML Build Templates in TFS (via Integration Build field of WorkItem. In the below screenshot it was mentioned as 'Integrated In'). We are currently trying to migrate from XAML Build Templates to vNext version of VSTFS 2015 and further to integrate with Octopus Deploy for CI/CD practices.
We are now half the way in the migration because we are stuck up making this vNext templates to associate TFS WorkItems with their Build numbers. Without doing this step, if we complete this migration, it will be difficult to get associated build numbers for each Work Items delivered in that build.
When we searched MSDN blogs, we got a post (link given below) similar to our requirement but I tried that and ended up with no luck.
https://blogs.msdn.microsoft.com/tfssetup/2016/05/09/build-association-with-work-items-in-vnext/
So, please suggest the ways which can resolve our requirement.
Since you are going to migrate from XAML build Templated to vNext. Suggest you also upgrade your TFS version to higher all together.
Just as Daniel point out TFS2015 released already 4 years, kind of little old. Same latest feature in TFS/Azure DevOps are not supported.
What you are looing for is a build-in option in TFS2017 update2 and above version.
Automatic linking from work items to builds
With this new setting in the build definition, you can track the
builds that have incorporated your work without having to search
through a large set of builds manually. Each successful build
associated with the work item automatically appears in the development
section of the work item form.
To enable this feature, toggle the setting under Options in your build definition.
More details refer this blog.
Besides, you could also take a look at our official tutorial Migrate from XAML builds to new builds in case you need.
I have been responsible for administrate our TFS projects and have started to investigate the current configurations. I found the following link for determining which process our team projects are connected to: How to determine what Process template an existing TFS 2012 project is configured with?
When using the rest API described in the article above, it seems like the projects depend on a process template called "Microsoft Visual Studio Scrum 2013". When reading this article: Scrum process it seems to me that the process is outdated and should be upgraded to use the "Scrum" template.
I have searched the internet for knowledge on how to upgrade the project to use the new Scrum process but had no luck of finding an answer. Does anyone have an idea of how to update the projects to depend on a newer process? Maybe the whole question is wrongly put as I may lack some obvious knowledge about how these things are meant to work. All I want is to ensure our projects are updated to use the latest TFS technology.
We use Visual Studio 2017 and did recently upgrade our TFS server to TFS 2018.
In general, some new features will be introduced when upgrade from old to new version of TFS.
Generally if you haven't made any changes to the original process template, upgrading is quite easy. Just enable new features by running the Configure Features Wizard in your team projects configuration page.
If it can’t upgrade automatically, you need to apply updates manually. See Add updates to team projects manually.
If you customized the process template, then you can follow the steps mentioned in this link to Update a customized process template to access new features.
To update the existing projects, a not so nice but easy way is to remove all work items and process data from your project and then add the newest items. Martin Hinshelwood has some great guidance on how to do this.
I am working on a TFS Implementation where the original Project that was created has a cpace in the name. This is causing issue in our builds since we need to kick off a batch file for the Deploy process and the space in the name creates some issues with the path name of the build folder. With this, I want to create a new project without the space. As you can imagine, I would like to keep the revision history of the Source Code if possible.
I have looked at this StackOverflow
Team Foundation Server - Moving Source with History
But I am a bit confused about what I would need to do. Is there someone out there that can point me to a document that is more friendly to someone who doesn't have a lot of TFS experience.
We've been faced with a similar task and we've used the TFS Integration Platform which might be of use to you.
Here's a couple of good blog posts on how to use it:
TFS Integration Tools - Part 1
TFS Integration Tools - Part 2
I have recently learned about continuous integration. From my understanding, its a way to automatically push code to a test environment once code is checked in. Then, you can eventually easily push that code to a production environment.
Currently, I am using TFS for my source control for an ASP.NET MVC 3 project. My question is, what are the recommendations for continuous integration. Unfortunately, I do not have a budget to actually buy something. With that limitation in mind, what do other devs recommend?
Thank you!
Since you are using TFS you should be able to do continuous integration with team foundation without the need to buy anything else.
TeamCity is very popular, and free for up to 20 build configurations.
Version 7 was released last week and includes lots of new features such as NuGet packaging.
I have been created a web project on tfs server and set a build for this application, which builds the application daily. I want to give a specific version of build to testing team, but if that version was build successfully before two or three days, how can I get the source code of that particular build which was build successfully a few days before.
If I understand correctly, you'll need to roll back to the Changeset you are looking for. This artcile will explain how to do that.
http://msdn.microsoft.com/en-us/library/ms194956(VS.80).aspx