|
||||||||
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 |
[JIRA] (JENKINS-5714) Additional options for tfs plugin such as overwrite and forced
kyle.james.ocon...@gmail.com (JIRA) Tue, 18 Sep 2012 15:06:56 -0700
- [JIRA] (JENKINS-5714) Additional optio... kyle.james.ocon...@gmail.com (JIRA)
- [JIRA] (JENKINS-5714) Additional ... kyle.james.ocon...@gmail.com (JIRA)
Yes, when you are doing a incremental get ("use update" is checked for this plugin) and you specify "/overwrite" and "/force", it ceases to be an incremental get at that point. Just "/overwrite" may be okay to fix OP's problem but "/force" will cause all files to be retrieved not just the changed files. So we definitely cannot use "/overwrite" and "/force" options in conjunction with "use update".
@OP, it sounds like you need to run a clean first if you are going to use incremental check outs. If you find yourself marking your source-files as not read-only then you will have problems because TFS relies on that flag to function properly.