Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X
Hi everyone,
we're using Integrity 10.1 on OpenSuse 12 and Hudson 2.2.1 on Windows XP with the Integrity-Plugin 1.16.
It occurs sporadically, that Integrity don't synchronize several members. Sometimes an older file is on hdd, though the plugin write in the log, that the new one checked out. Sometimes new member are not checked out actually.
The option "clean workspace" decelerated the build-process and didn't resolve it at all time.
I can't find helpful informations in the log-files. Maybe someone can help?!
We face the same problem.
(Integrity 10.2 , Windows Server, Jenkins 1.523, PTC-Plugin 1.17)
That's why we use the "clean workspace" option only and disable all other options in all our build jobs.
This is sometimes painfully slow ( in peaks it take over 20 minutes just to update the workspace) but at least for nightly builds it's a workaround ( "better slow, than insecure" ).
The Jenkins plugin is at as far as I know, not officially supported by PTC, and as it is open source you are free to improve it at will or at leat the log-file output.