In TFS2008, is there anyone to tell the Warehouse Controller job to do a full rebuild of the Analysis Services Cube everytime? I know this can be done in TFS 2010 but I can't seem to find any information regarding this for TFS 2008.
If not then would it be a bad idea for me to schedule in a task to manual rebuild the cube just before the warehouse job runs every 5 hours or so ?
Related
We have migrated our Team Foundation Server from 2013 to 2017 recently. In previous version there was no Data Warehouse or reporting configured.
After moving to TFS 2017, we configured Data Warehouse and Reporting services which went fine without any issue.
Now issue we are facing is, in reports we are not able to see any Build related data, only data we see is from old XAML build and nothing from new TFS 2017 build.
when I looked into DimBuild table of TFS Warehouse, it has only old data no new rows.
we tried to re-create warehouse and re-start TFS Warehouse services from Warehouse Administration link, but nothing is helping.
Anyone has any idea?
You can retrieve the data through REST API and do reports or you can get the data from collection database for reports.
You're not seeing it because it's not supposed to be there.
The data warehouse does not contain information for non-XAML builds, nor does it contain any release information.
I'm using TFS 12.0.30723.0 and I'm trying to build a query on which I can see the history of all the changes on different tasks for the current sprint for a person. I don't know why the #CurrentIteration is not accepted, so probably I'll change the sprint param in the query when needed. I want to see how many hours have been completed and on which day of the sprint for a person assigned tasks. Basically a history on how many hours and when have been completed.
What I've tried until now, looks like:
Is this possible to accomplish on TFS?
In this MSDN document, the #CurrentIteration is only could be used in the following clients:
Web portal that connects to VSTS
Web portal that connects to an on-premises TFS 2015.
Visual Studio 2015 connected to TFS 2015 or
VSTS.
You're using TFS 12.0.30723.0, this is TFS 2013. #CurrentIteration doesn't work for TFS 2013 web port. You could upgrade your TFS to TFS 2015 or higher versions.
About your request, you could add the AuthorizedDate, RemainingWork, CompleteWork field column in the query result. Then you could export your query using Excel to Sum up. Because TFS query doesn't have the calculating feature. The AuthorizedDate shows the time when the workitem is assigned to someone.
Can anyone share a .bak file of TFS complete collection to test and see the options of burn down and iteration velocity, but don't have enough data on one day. I have downloaded the FabrkPrice.bak but it was for TFS 2013 and I have to update TFS, I want one for TFS 2012 please
For TFS, there have always been the Brian Keller VM's. There are downloads for every major version of TFS:
2015: http://vsalmvm.azurewebsites.net/
2013 & 2012: https://blogs.msdn.microsoft.com/briankel/2013/04/17/list-of-all-visual-studio-alm-virtual-machines/
For VSTS there are a few alternatives. One is to import the Brian Keller VM into VSTS. You'd have to upgrade it to 2015 update 3 and would probably need to tweak the work item schema a bit. The problem with this solution is that while the Brian Keller VM's always start at the same point in time, your VSTS account will start to lag. So while the diagrams and graphs all look nice now, they're going to be behind after a week.
OpsHub TFS Migration tool
Microsoft High Fidelity Import (currently in closed beta)
Another option is the Sample Data Widget. It can be used to pre-populate a VSTS account with data so that it looks good for demo purposes. It doesn't populate all the kinds of data you'd get from the Brian Keller VM, but you'd get a nice backlog and burndown:
https://blogs.msdn.microsoft.com/visualstudioalmrangers/2016/03/25/sample-data-widget/
https://marketplace.visualstudio.com/items?itemName=ms-devlabs.SampleDataWidget
We are migrating 60 Thousand workitems from TFS 2010 environment to 2012 environment using the TFS Integration tool. In the test environment is took very less time as less traffic was there , but in production environment it is taking more than 2 weeks as calculated by the current speed it is going in.
Is there anything we can do to speed up the migration ?
How does the tool works to migrate these workitems ?
You can add new query in TFS Integration Tool to reduce the amount of work items to be migrated at one time.
I am told TFS can accept data on build/test metrics from 3rd party continuous integration tools. Does anyone know how this works or have any good links for me? My google-fu seems weak today and I cannot find any info on this. We would like to have a short powershell script or app run at the end of the build and send all known metrics up to TFS so it could show up in certain reports. I actually would like things that (I think) should already have space for in the data warehouse for TFS BUild Server, but I will be using CC.NET. I am thinking build name, result (Pass/Fail), Number of Warnings, Number of Errors, Time, UnitTests Run, UnitTests Passed, Code Coverage, FxCop resultsThanks.
I'm afraid that there is not a ready made integration that does this yet. The plug-in that links CC.NET to TFS is available over at CodePlex but this just lets CC.NET use TFS for version control and doesn't allow the results of the builds to be published back into TFS.
To get the data into TFS from CruiseControl.NET you have a couple of options. You could write your own custom TFS Data Warehouse Adapter which is complex but ultimately flexible or you could use a combination of the Team Build API and a little bit of vodoo to push data in to the TFS Build store that would also get pushed into the TFS Data warehouse. However, this would be limited in TFS2008 as you would only be able to push data about the build and the unit tests but not things like Code Coverage.
That said, pushing data from CC.NET to TFS is something that I originally wanted to do. However in TFS2008 the built in build system was so good that I switched from using CC.NET to trigger the builds to using TFS to trigger and manage the build. This had the advantage that all the stats stuff was taken care of automatically (and the built in UI in Visual Studio). Because I moved to TFS2008 I then lost the motivation to get the CC.NET stuff built.
If anyone wanted to contribute a TFS build result publishing feature to the CC.NET integration then feel free to join the project on CodePlex - I would love to have any help going.