It is building the builds at a time that is five hours ahead of the actual time. I have remoted to the Server box and the time on it is correct. How can I get TeamCity to build in the correct timezone?
Usually, TeamCity shows the time in the Server's local time.
On the My Settings & Tools page, there is a setting, which enables showing times at current user local time. So if you've enabled this setting and your machine is 5 hours ahead from Server's time, you'll see time which is 5 hours ahead.
Related
Has anyone else encountered this problem:
Every month I apply windows updates to servers using SCCM Software Update Groups. Some servers are considered lower priority so I push the updates as required to the server and expect the updates to install and the server to reboot if necessary during its assigned maintenance window only to find out that the some of the updates are failing. With experience, I have found this is because the system is waiting for a reboot. I would expect that SCCM would know that there is a pending reboot and reboot the server during the maintenance window to finish applying the updates but it does not. It seems as though these are "pending reboots" that SCCM cannot detect.
As a result, this requires manual intervention each month on a dozen or more servers that have to be manually rebooted in the middle of the night so as to not interrupt production.
One of the biggest culprits to this issue is the monthly Malicious Software Removal Tool. It always seems to fail to apply then works after a reboot.
The Computer Restart related setting can be configured in the "Client Setting" node on your console. No matter if you determine to use the Default client setting or the custom client settings, you should make sure that that the value for the restart temporary notification interval and the value for the final countdown interval are shorter in duration than the shortest maintenance window that is applied to the computer (the default values are 90 and 15 mins). This is important for the deployments which require a reboot completed on your clients.
Additionally, you can examine the logs on the client-side as below:
Update deployments related logs: UpdatesDeployment.log, WindowsUpdate.log
Reboot & Maintenance related logs:RebootCoordinator.log,ServiceWindowManager.log
More details about how to track the Update deployment process in ConfigMgr can be found here.
Sometimes, I see that my workspace are updated alone.
Cloud9 says: "Updated X time ago", but I have no more information.
It may be an error of Cloud9? This happens to me in workspace that I'm alone and I've already changed the password.
Does this happen to anyone else?
UPDATE:
Response from Cloud9.
"Hi Sebastian,
Thanks for getting in touch about this issue. I looked into your issue, and it turns out to be our automated backups. We actually take periodic backups of both active and inactive workspaces, and this updates the "updated" time stamp. I'll talk to the teams about not updating the time stamp when backups are performed. This should be very helpful to avoid any future concerns users may have :)"
I am running into a problem with viewing the build logs while a build is in progress.
The build is being run on a seperate (continious integration build) machine and we are using VS2010 and Team Foundation Server to manage the build from our development client machines.
The problem is that VS2010 will poll for the logs on the build server and update approx every 30 seconds. The solutions that are being built are pretty big and there are a lot of them. They generate a lot of warnings and logs at the moment which bloat the log considerably. Because of this it is nearly impossible to use VS2010 to view the build log until after the build has completed which is approx 85 minutes.
Obviously - a solution would be to fix up all the warnings, but I was wondering if there is a way to prevent the build log viewer from polling - just list all the detail until a 'refresh' is requested or even a way to extend the poll to say every 5 minutes would work for me.
I understand that the build log no longer gets written out to disk in VS2010 - so I can't access it unless I go through the Build Explorer.
Any thoughts would be very much appreciated!
Jay
It is possible, please have a look at this useful post written by Jason Prickett You will be able to change the polling interval by adding a DWROD 'ReportPollingInterval' at HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\TeamFoundation in the registery. Values to the DWord are assigned in milliseconds, so 30000 would mean 30 seconds.
Also consider installing VS 2010 SP1 on your machine, the SP1 has addressed a lot of performance issues with the build summary page.
Bounce back if you have any follow up questions.
We're running TFS 2010 on a dedicated machine. The SQL db is also running on the same machine so there is no external LAN/WAN access there.
When we check in/out or get anything from TFS - the initial connection and any connections after some inactivity from VS is extremely slow, sometimes up to 1 or 2 minutes. Once it does whatever it has to do, things start run fast and move along with no problems whatsoever.
What/where should i check to find this bottleneck, or whatever it is that's turning off after inactivity ?
I think that it is similar to SQL Server Reporting services. When it is inactive for some time (20 min?) the worker process fall asleep and wake up time is rather long.
SSRS 2008 - Long delay after a period if inactivity, How to Speed up MS SQL Server Reporting Services SSRS on First Run. There should be similar setting for TFS webservices.
I suspect it is the traditional ASP.NET wakeup pipeline that you are running into. If you want to try out setting a scheduled task that runs PingTFS.exe then it will keep the site loaded so that you don't see this initial hit each time the TFS web services have cooled down.
You can find PingTFS.exe available from Neno Loje here: https://msmvps.com/blogs/vstsblog/archive/2011/03/02/how-to-ping-tfs-to-see-if-it-s-up-and-running.aspx
If that doesn't help, then it's likely the hardware in the environment. You definitely don't want to have too few of resources for your TFS environment. Let us know if the first suggestion doesn't work out.
I am working with espresso for Mac, and I've found that I may have a problem with publishing tools.
My server is located at the USA, but I, and my computer, are located in Spain. So when I modify a file in my computer, and then one of my partners edits it again in the USA, if I do a sync, I erase his file with mine ... even being mine older.
I think that this is happening because my TIMESTAMP is in GMT+1, while server and partners time is GMT-8 (California), so their file will only be newer than mine if they touch it 9 hours later.
How can I fix that??
Thanks in advance!!
In Espresso 1, go to the server's preferences and expand advanced settings (could be named something different, I'm working from memory). There should be a button to detect the time difference between your computer and the server. Use that and you should be good to go. I think Espresso 2 does this automatically now.
If you continue to have issues, send a message to support#rhinointernet.com. They like to take care of FTP issues over email.