i have stopped getting new entries in my reports, even though they appear in the list of builds.
I've only added a task to create a directory & make a dummy exec call to do a "dir"...
Build still succeeds...
OOps...here come the new entries...
Like someone in the other thread said, there's some sort of cacheing going on...
any way to switch it off then or reduce it/force it to calculate it all etc.?
Thanks
OK, one more question.
Only the succeeded builds show up.
Is there a way to show all - failed & succeeded - builds in a report?
OK, found that setting. See if it actually works now.
Didn't work straight away...I'll just wait.
Hi Buck,
Thanks for the reply...
The reports eventually show up, but it seems the cacheing problem is not sorted...
The cache settings don't allow you to change that behaviour..They look like they're set correct but there's a bug somewhere or something.
The latest builds show up whenever it feels like it...sometimes takes a few minutes ... which is very annoying!!! Not sure exactly when.
Also, I can't seem to find a way to show up the builds that have failed in the reports. :(. I would have thought that'd be part of the out-of-the-box report...I didn't really want to try to create a custom report at this point. I'm not really setup for it yet, and didn't want to go there right now.
Another place I didn't want to go was to write my own task for customising the build number. The SDC Build used to use/support the Major.Minor.Build.Revision format for build numbers. I would have thought the build number task would have had some sort of format specifier to set the build number etc. It currently just puts the date and a single incrementing digit which is not entirely useful I don't think. Again, I would have thought this'd be out of the box...
We're using TFS on a webMethods implementation, so it's not your typical .NET shop implementation...:(
It's a good test for the product though. Also great for the team as TFS is so way cool!!!
The delay is probably the time it takes for the data to propagate to the warehouse and be processed.
We're hoping to improve the handling of build numbers in a future release.
Thanks for the feedback.
Buck
RE: Delay...?
OK, I can see that the server is running on borrowed RAM !!! Which won't help my cause any...
Even though CPU is low, disk is prb. dying...as avg. disk Q length is often above 1.5, and out of the 1GB of Physical RAM that it has, its using 1.6Gb etc.
All I'm doing it a get of stuff every 5 mins (imitate shadow directory etc.).
And a test build every day - very light - one simple webform etc.
Other than that I've got VStudio open etc. in a Terminal Services Session. Check-ins & repository operations are minimal though.
Anyway, this is just a test server for TFS evaluation. We'll be migrating over to the proper dev server next week or so, so that should see some of this stuff go away.
In the mean time, I may go tell SQL Server to stop hogging as much RAM!!!
Currently got about:
373MB working set
1.1GB! Virtual Memory, of which 553MB is Private Bytes etc...I might try limiting SQL Server to say, 512MBytes or something, see how it goes...
OK, now 256MBytes. Geez it's awesome to be able to adjust this stuff on the fly!!!
To me, it seems the server is doing pretty much nothing most of the time, so I don't see why there'd be such a delay in the reports. Maybe SQL is not coping very well with the lack of RAM.
When it's not doing stuff though, avg. disk q length is less than 0.01 and I still don't get my reports. There seems to be some sort of internal timer or something...that ignores some of the report settings (i.e. the "always show me most recent data...").
Anyway, I'll just have to wear that for the moment & hope that SP1 fixes it.
Also, w.r.t Builds... there's no chance of getting the source to that by any chance is there?
I'd hate to build my own build number generator & either miss or have to re-code all the stuff you guys have already built...
The warehouse gets updated on a timer. You can manually kick it or change the interval (http://blogs.msdn.com/echarran/archive/2006/04/26/584152.aspx).
Here's a post on creating custom build numbers: http://blogs.msdn.com/manishagarwal/archive/2005/07/13/438077.aspx
Buck
Hi Buck,
RE: Timer. Thanks. At least now I know how it works & it explains the behaviour etc.
Unfortunate about the failed builds etc.
RE: Builds...I actually found that link & am in the process of doing the actual build.
One of the issues I have is obviously getting the last build number. I was stuck for where to get this info from, so reverted to my old habit of creating a file to manage it. It's not ideal, and since TFS already knows this, it'd save me a lot of mucking around if I could get at it somehow...Is there such an API?
ps. My current problem revolves around checking in & out a file with the build number in it. Those tf commands work fine from the command-line, but when they get kicked off by the build service, the different workspaces come into play & are giving me some grief at the moment. I'm sure I'll sort it out, however it's a problem that I shouldn't have to worry about. i.e. If I could just get the last build number for that build type from TFS, I wouldn't have to do all of this in the first place...
Cheers & Thanks.
