I have a server with TFS2015.1 installed and since this update I have added some git repositories to an existing collection.
Historically it was using TFS version control, but more recently we have started to look at using git more prolifically, and because of this I believe the alerts available do not include a pull request option.
Is there something I can ask our ALM team to try.
I am hunting for a template change if possible, is this something that an update x of TFS might allow.
I have to consider the possible of needing separate collections.
This is a known issue with TFS 2015 Update 1. It has been fixed in TFS 2015 update 2. There is no solution to fix this on Update 1 other than upgrading the TFS instance.
Related
Currently we are using TFS 2017 update 1 on premises but we have to Migrate TFS at VSTS cloud platform. Also we TFS Build Servers on premises having XAML builds using customized build template. Our problem is after migration all XAML build definition would working as usual or not?
Currently we are using TFS 2017 update 1 on premises but we have to Migrate TFS at VSTS cloud platform. Also we TFS Build Servers on premises having XAML builds using customized build template. Our problem is after migration all XAML build definition would working as usual or not?
there is no code. Do we need to Re-configure all build server again?
After migration on VSTS can we configure All build servers on premises as well using old all XAML build definitions or not?
Please suggest on this.
XAML builds are still supported with Azure DevOps Service (with some limitations), see official response from Microsoft:
XAML build is still here until now. Current state :
If you have any XAML build data in your team project collection, you
will 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 will need to install them using the TFS 2015
build agent installer. Please refer to official document -XAML builds:
https://learn.microsoft.com/en-us/visualstudio/releasenotes/tfs2018-update2#xaml-builds
And we will keep it longer, how long does it can be used depend on
user feedbacks.
Installing TFS2015 Update 4.1 locally allows you to configure Build Server, Service and Agents that are connected to Azure DevOps Service, and run all your XAML builds from either Azure DevOps or Visual Studio.
XAML builds are no longer available in VSTS, so they will not work at all after a migration.
The good news is that TFS 2017 supports build vNext so you can convert your builds before you migrate to make sure you can still build after the migration.
Build vNext (Azure DevOps Pipelines) are much more flexible and easier to set up and customise than the old XAML builds. However if you have a lot of customised builds then it might take a while to convert them all.
One big advantage of the new build system is that the same build can be used across multiple branches, which might mean that you don't need to put as much effort in to converting builds as in the XAML system you needed a build per branch.
My suggestion is that you begin by familiarise yourself with the new build system and start to convert the builds before you migrate, then you can import you TFS database in to VSTS.
I get this error in the TFS logs when I try to upload a task in the new TFS build system using the tfx-cli tool:
Microsoft.TeamFoundation.DistributedTask.WebApi.TaskAgentVersionMismatchException:
The task definition being uploaded requires a minimum agent version of 1.88.0.
The server's agent version is 1.83.2.
Unfortunately that is the agent that TFS provides for download.
It is an On Premise TFS server.
Does anyone know how to get the 1.88 version of the agent?
I did modified the task json file and I was able to upload it however it did not show up in the TFS UI.
And the reason is here:
https://github.com/Microsoft/tfs-cli/issues/30
In summary I was trying to use IISWebAppDeploy task which from the official git repository but that task is still in development and it will not show up in TFS until marked for release.
I suppose 1.88 is the current version of the VSO build agents. At least if I login to my VSO project and switch to the Hosted pool, the hosted agent is of version 1.88. I suspect it is being upgraded by the VSO silently. Thus, if you download an agent from VSO one of these days, it will most likely have version 1.88.
However, I'm not sure it is a good idea. First verify whether you really need a more recent version. The minimalAgentVersion is defined in the custom task definition, the JSON file. Try changing it down to your agent version, 1.83.2. Most likely, you should not require a higher version of the agent in your custom task until you upgrade your TFS instance.
I am in the situation with the environment.
VS 2013, Update 4, CTP 3.1 Cordova.
I have been struggling for the past 1 week to publish the app to stores as it is stopping with error
"The package identity associated with this update doesn't match what's in the uploaded package".
Some gentleman has suggested to update to 2015 and ctp6 to pass through this problem.
Any alternatives that I can get here?
I tried all alternatives but could not get pass through this.
Thanks
If this is for the Windows platform (and I assume it is based on your tags), try installing this workaround plugin:
https://github.com/Chuxel/taco-tricks/tree/master/plugin-windows-package-fix
This should be resolved in VS 2015 but is an issue in VS 2013.
I made a TFS custom build definition, in which, among other things, the projects sources are zipped in a delivery directory.
I'd also like to download the latest version of the documentation from the TFS project sharepoint documents collection.
As the DownloadFile seems to be version control centric, I tried to use an InvokeProcess activity, coupled with a wget call, but I'm facing authentication issues.
Am I missing a dedicated activity which may solve this issue?
I ended up giving access to the Sharepoint website to the account running the build service, and putting this account credential in the wget script.
Not a very good solution, but a working one nevertheless.
I have developed a s/w using acces and sqlserver 2008 and now trying to make a setup file.
How could be the possible way??
I tried in VS2008 software and development. But after installing from the msi file and running the s/w it shows an error
"Microsoft.ACE.OLEDB.12.0 provider is not registered”
plz help
You have to do a few things to set up your application:
Install the .NET framework if required
Install SQL Server 2008 if required
Install your application
Define/configure the connection from your application to the SQL Server instance
Create your database/schema in the SQL Server instance.
Ignore the SQL Server problem for a moment, the easiest way to deal with the .NET framework and installing the application would be to use a setup project - which should be available from within VS.NET under Other Project Types|Setup and Deployment. There are hooks in there to give you options for installing dependencies - of which the .NET framework is one.
Ok, you have a tool to create setups (there are several others, e.g. I'm currently using WiX which I like so far, is very capable but can rapidly becomes complex) - the problem now is that the installer you need to build will depend on how and where your application is to be deployed. Do you want to ship a complete, self-contained, application on a disc? Is it to be downloaded internally within a business or distributed over the internet - each of these suggests a different set of packages at one end "everything" at the other you want the smallest possible pieces pulled down as required or perhaps even a different packaging method (e.g. clickonce).
Next up is SQL Server. You can get a redistributable package for SQL Server 2008 Express, so distributing it is not a problem however you have to determine if the user has an existing instance they want to user or if they want to install.
Once you've got an installed instance - you need to be able to create and to maintain (update) the database/schema within that instance. That I suggest you do using code (see here: How to create "embedded" SQL 2008 database file if it doesn't exist?). Which brings us to another point, you not only have to be able to install the application the first time, but you need to make sure that a) you provide a means to uninstall the application and b) that you can neatly do an upgrade in place.
I hope there are enough pointers there to get you moving - in terms of testing this, Virtual Machines are your friend, they give you the capability to create multiple environments in which to test your deployment and the ability to quickly roll back to a clean environment to test again as its virtually impossible to properly test an installer on a dev box (I've found this out the hard way) as it will already have all the dependencies for your application installed.
Pick your tools and that should let you ask more focused questions.