У нас вы можете посмотреть бесплатно How to Ignore a Folder During SVN Checkout или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Learn how to effectively ignore specific folders during an SVN checkout using sparse checkouts. This guide provides step-by-step instructions for build automation. --- This video is based on the question https://stackoverflow.com/q/192824/ asked by the user 'Zote' ( https://stackoverflow.com/u/20683/ ) and on the answer https://stackoverflow.com/a/218131/ provided by the user 'Jon Topper' ( https://stackoverflow.com/u/6945/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions. Visit these links for original content and any more details, such as alternate solutions, comments, revision history etc. For example, the original title of the Question was: SVN checkout ignore folder Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l... The original Question post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 2.5' ( https://creativecommons.org/licenses/... ) license. If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com. --- How to Ignore a Folder During SVN Checkout: A Practical Guide Subversion (SVN) is a popular version control system that allows developers to manage changes to their code over time. However, there are times when you may want to ignore certain folders during the checkout process, especially on build servers where you might want to prevent unnecessary files from cluttering your workspace. One such scenario could involve not wanting to include the DOCs folder when checking out code. In this post, we will explore a solution to this problem: sparse checkouts. Though SVN does not directly allow you to ignore folders during checkout, with sparse checkouts introduced in version 1.5, you can effectively control which parts of your project to include. Understanding Sparse Checkouts Sparse checkouts allow you to selectively include directories and files when checking out a repository. This method is particularly useful when you only need a subset of the project for building systems or for development purposes. Step-by-Step Guide to Performing a Sparse Checkout Start the Checkout Process Begin your sparse checkout by executing the following command in your terminal. Replace the URL with the correct path to your SVN repository: [[See Video to Reveal this Text or Code Snippet]] my_checkout is the local directory where you want to check out your project. The --depth immediates option checks out the immediate children of the specified URL but does not recurse into them. Check Your Directory Structure After executing the command above, navigate into your newly created directory: [[See Video to Reveal this Text or Code Snippet]] You should see a list of directories (e.g., bar/, baz, foo, xyzzy/), but none of the contents inside them have been checked out yet. This effectively means that larger directories like your DOCs folder are not included. Include Specific Directories If you decide you need some of the files or folders that you initially skipped, you can include them later. For instance, to include everything from the bar directory, use: [[See Video to Reveal this Text or Code Snippet]] This command sets the checkout depth for the bar directory to infinity, retrieving all files and subdirectories. Conclusion While it may seem cumbersome at first, using sparse checkouts in SVN allows you the flexibility to manage your checkout process without downloading unnecessary files. By selectively including the folders you need, such as ignoring large documentation directories, you can streamline your builds and improve efficiency on your servers. For developers utilizing externals, remember this method works seamlessly while still providing access to necessary dependencies. Next time you are faced with a similar requirement, try this approach to maintain a clean and efficient workspace.