Up to TFS 2017 there was a library in Plugins folder called Microsoft.TeamFoundation.Framework.Server it contained ISubscriber interface which one could override in order to attach hooks and add behavior for events such as build completed or new push to the git repository. The library is missing in TFS 2018. Does anyone know how do we maintain our plugins now?
The library is still there, just under the TFS 2018 install directory. If you’re deploying your plugins into TFS 2018 you will need to recompile them against the 2018 references.
We have several plugins subscribing to WorkItemChangedEvent, Git PushNotification event and BuildDefinitionChangingEvent and they all work up to and including TFS 2018 Update 3.
Related
I have been working on TFS 2017 update 3 from past couple of years and now I have started working in new team where they are using TFS 2015.
In TFS 2017 Web, all the Build Definitions we had we used to keep\save them into their respective folders as their was option of Manage Folder present under Build Tab but here in TFS 2015 Web, I don't the see the option of Manage Folders and have to keep\save all the Build Definitions under one tab.
Is there any extension available in the marketplace or way by which I keep all the Build Definition in a more organized way in TFS 2015?
I am afraid Manage tfs2015 doesnot support Manage Folders feature. And I failed to find an extension that was available on the marketplace to achieve this.
You need to upgrade tfs2015 to a newer version in order to use the Manage Folders feature.
You can check out below document for more information:
Upgrade your deployment to the latest version of Azure DevOps Server
We installed the newest TFS Server (TFS 2018 Update 2) which should run xaml builds.
After the update, we started our agent, but our xaml-controller is still offline and I don't know how I start this again..
Any ideas what we can do?
Yes, you can now upgrade to TFS 2018 Update 2 and continue to connect
your XAML controllers and run XAML builds. When we removed support for
XAML build in TFS 2018 RTW and Update 1, some of you could not upgrade
due to having legacy XAML builds, and we want to unblock you. Although
TFS 2018 Update 2 supports XAML builds for your legacy builds, XAML
build is deprecated and there will be no further investment, so we
highly recommend converting to a newer build definition format. See
the Evolving TFS/Team Services build automation capabilities blog
for more information about XAML build deprecation.
When you upgrade to TFS 2018 Update 2:
If you have any XAML build data in your team project collection,
you'll get a warning about the deprecation of XAML build features.
You will need to use VS or Team Explorer 2017 to edit XAML build
definitions or to queue new XAML builds.
If you need to create new XAML build agents, you’ll need to install
them using the TFS 2015 build agent installer.
XAML Build Controller/Agent info is now under Additional Tools and Components > XAML Build Configuration in the TFS Administration Console. Make sure your build services on the same server as your application tier. You possibly didn't re-configure your XAML build services after the upgrade. Try this and then check again.
Thanks #PatrickLu-MSFT!! through your help, we found a workaround.
Now we use one server for the Source Control etc. (TFS 2018) and another server only for the xaml-app-controller with TFS 2015.
So we can build our projects, and have time to create new build definitions.
If the repository is git behind our TFS project there is no way to filter the repository by source folder. The build always pull the whole repository. We have multiple solutions in the TFS project we want to build separetly. We can do it, but it is slow because we cannot filter the source folder to download.
The other problem that we cannot add folder to CI trigger. So all the projects will be build after a push in any projects.
I know that the Team Services already support path filters for git repository. But does anybody know some workarounds for this problem for on premise TFS 2015 Update 3?
There is no workaround for this on TFS 2015 update3. Unless separate your components into different repositories. Multiple projects must be in their own repository. All dependencies is a project by it self and can be handled as NuGet packages. Then your whole solution would not break if you change something in the dependency project and using CI trigger.
This feature will ship in TFS 15 and is already available on VSTS
https://www.visualstudio.com/en-us/docs/build/news/2016#june-14
We currently use TFS 2013.
I'd like to do a POC where I can create some build definitions in TFS 2015 where it would get the source from our existing TFS 2013 server. Once the boss sees how much easier it is to manage our builds from TFS 2015, I'm sure he'll give us the go-ahead with upgrading the existing TFS 2013 to TFS 2015.
Is this even possible?
You could write a PowerShell script or some batch files to leverage tf.exe in order to map a workspace / clone a repo (depending on whether you're using TFVC or Git) as part of a build. Or just put the tip of your source code into the "demo" environment and build from there. The latter option is going to be much faster.
I've got TFS 2015 running with Git repos using the new (non-XAML) build process. Is there some way to trigger a specific build when a new tag is pushed to the Git repo? The filter seems to only accept branch names.
Update Microsoft has responded that it should be possible using the following as as a trigger:
refs/tags/*
or:
refs/tags/<tagname>
But apparently it is not yet in the on-prem version of TFS.
Old answer
TFS 2015 Update 1 doesn't have the possibility to trigger a build when a new tag is pushed.
TFS 2015 Update 2 is released not long ago, but I don't know if that version support tags or not.
Since I couldn't find any uservoice issue, I created one