Windows and MAC differences + Cache flush

Hi all,

I was developing (in a Windows machine) a plug-in for Team City. I deployed it in another Windows machine to test it with success. However when I deployed to a MAC box it didn't. Moreover I tried to track the error and somehow it seems that the next versions of the plug-in that I put in there are not taken although the system shows me the latest. Therefore I would like to know how to get clean the possible cache that Team is using or how to force it to take the latest zip that I deploy.

Thanks a lot!
Carlos.

4 comments
Comment actions Permalink

Not sure I understand the problem. Do you mean that TeamCity does not see the latest version of the plugin even if you update the zip file? Do you deploy your plugin under .BuildServer/plugins directory? Note that server must be restarted if new version of plugin is deployed.

0
Comment actions Permalink

Sorry if I was unclear.

What happens is that I'm deploy on Windows at <myUser>/.BuildServer/plugins. In MAC I also deploy at /.BuildServer/plugins. Once I do the deployment in both systems I restart the service and then TeamCity can take the changes. In Windows works correctly, without any issue and the features added by my plugin do work. However in MAC they don't. We have tried rebooting the MAC machine, delete the .unpacked folder, check the dates within the files to verify that indeed the latest version is being taken but still doesn't work. We are using Windows 7 and Mac OS X if it is useful.

That's why that even restarting the machine, it appears to be executed in the stack trace of the expection that we get, some code that it shouldn't be executed as is not there anymore.

Any idea?

Thanks again!

Carlos.

0
Comment actions Permalink

Could you please provide teamcity-server.log from the MAC server installation? I would also suggest to install new version of TeamCity on this MAC machine and run it with the same .BuildServer folder, just to make sure there are no any forgotten resources. Maybe you could also describe in more details how do you check that the version of the deployed plugin is out of date.

0
Comment actions Permalink

Hi Pavel,

I checked that again yesterday and it was working. Apparently something remained in the cache because was strange that even we changed the code, the error message was still there. Even after rebooting the machine. Now is working fine, so everything sorted.

Thanks anyway!!

Cheers,

Carlos.

0

Please sign in to leave a comment.