|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Thanks for the update Rob. We can try the quick clean option.
But I'm not sure if there will be any issues since we're planning to use this against a read only replica perforce instance, where the client workspace won't have any status of the files synced on a host. If the quickclean option only tries to get a list of the files a client workspace should have, it should work.
But if it tries to check for status of sync or revision, then it likely won't work. Which might be what happens when the "Restore Changed/Deleted Files" option is checked with the quick clean. This option's description states
"This option will scan for any tracked files that have been forcefully changed or removed by some other process (build scripts, compilers, engineers, etc) and force sync them from the repository."
Either way, we'll give it a try.