After a part-migration on our Team Foundation Server 2017 Build/Release System, we now need a "Continous Release" for a scheduled XAML Build (as long we need the XAML Build).
First of all, I've put a trigger in my release definition.
After that, i've started the build manually --> the release works fine.
If the build runs scheduled --> no release is created.
If i try to manually release the scheduled build, the following execption occurs:
Is there any solution?
Related
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.
We work with TFS 2015 and it works really great. We have two different build sets one for our production environment and one for our test environment. We also use CI. Our current workflow is that we "Queue build..." and then everything is done automatically.
What we would like to accomplish on our production build is one of the following:
On "Queue build..." the person has to acknowledge the build or
You have to somehow start the queue manually, so the queue build doesn't start automatically
Don't use builds for deployment. If you're on TFS 2015 RTM or Update 1, upgrade to TFS 2015 Update 2 (or, ideally, TFS 2017 Update 1). Starting in TFS 2015 Update 2, there is a Release hub that has exactly the kind of capabilities you're asking for. It allows you to define a release pipeline for the binaries generated by a build, where you can put optional approval requirements in place prior to a deployment occurring on a given environment.
We used to get notification from the tray of our windows machine for a finished build while using the xaml build definitions, it also had an option to reconcile workspace. The same functionality is not available for the vNext builds.
The BuildNotification App is available with VS 2015, but it seems that the reconcile workspace is not available with the vNext build. Is there some other app that can give a notification and do the reconcile operation?
We just moved to new builds (vNext) and are missing this feature as well.
Currently, we can do this manually via IDE (VS 2015):
Team Explorer -> Builds
Right click on latest build with you changes -> "Reconcile Workspace..."
The BuildNotificationApp is still a part of the VS 2015 and can be found here: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\BuildNotificationApp.exe. However, this app only applied to XAML build.
For now, to workaround the missing feature, you can use a free build status tool Catlight . It also shows status of vNext builds in tray area.
As for reconcile workspace, there is no this build-in feature for vNext build. However, you can manually use tf reconcile command for your workspace. Such as below screenshot:
Update:
If you just want a simple app or vs extension to achieve it, there is no these things for now. You may have to customize your own extension to implement it.
Update2:
I have created a feature request in uservoice:
Reconcile Workspace for vNext Build
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/15979690-reconcile-workspace-for-vnext-build
You can use AnyStatus to monitor both vNext and XAML builds.
AnyStatus comes with a feature called Triggers which lets you run a program or a batch script in response to status changes. Using Triggers you can configure it to run "tf.exe reconcile" when the build status changes from Running to OK.
Disclaimer: I am the author of Any Status.
I'm starting out with continous integration with TFS 2013. I've added a CI build definition, and on each check-in of the code a build is executed. So far, so good. Next I'd like to get some kind of feedback; I can check in a test which fails, for example, and the build-server will fail it but there's not notification in my Visual Studio. How can I get a notification from the build server, straight to the developer who initiates the CI build?
You can set a build alert up in the portal to alert the user that their build's not succeeded (i.e. failed or partially succeeded)
http://yourTfs:8080/tfs/yourCollection/yourProject/_admin/_alerts#
In TFS 2013 I have Build A which compiles and runs unit tests. I also have Build B which deploys to a dev server. How can I start build B when Build A succeeds in TFS 2013?
You create a custom Workflow, Download the build Definition and then add the "Start Build"-Activity. Choose your build-workflow in the build-definition and voilà