- 1Android Studio使用Kotlin开发Android入门_android studio 的kotlin
- 2Ollama--本地大语言模型LLM运行专家_ollama 模型
- 3无需租云服务器，Linux本地搭建web服务，并内网穿透发布公网访问_linux apache2 .内网穿透
- 4文本向量表征工具，实现了Word2Vec、RankBM25、Sentence-BERT、CoSENT，开箱即用
- 5IntelliJ IDEA常用插件 提高开发效率_sonarlint 卡顿
- 6缓存踩踏：Facebook史上最严重的宕机事件分析
- 7【网络】gateway 可以提供的一些功能之一 “ 提供web静态资源服务 ”
- 8解决MATLAB显示failed to initialize java
- 9计算机应用技术的历史与现状,浅析计算机应用技术的现状及发展趋势
- 10vue2 el-select 改造成下拉树，支持数据回显_el-tree-select vue 2
jenkins如何清缓存,jenkins在结账前清除存储库并强制克隆与清理
赞
踩
I am trying to understand the difference between the two options “Wipe out repository and force clone” and “Clean before checkout” for pulling a git repo. Looking at the help section for both options, both seem to have similar functionality and I can't make out the difference. Here's how they look:
Wipe out repository & force clone:
Delete the contents of the workspace before building, ensuring a fully fresh workspace.
Clean before checkout
Clean up the workspace before every checkout by deleting all untracked files and directories, including those which are specified in .gitignore. It also resets all tracked files to their versioned state. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory, and ensures that your build is not affected by the files generated by the previous build.
I couldn't find any comparison between the two options; neither in Jenkins/GitPlugin wiki, nor in stack overflow, and not even in google. We currently have both options, but we are planning to reduce build time by removing the “Wipe out repository and force clone” option. But I don't want to break any functionality while doing this. Please explain the difference if you're sure. Thanks in advance :)
解决方案
Wipe out repository & force clone will clean the entire project workspace and clone the project once again before building. It could be time consuming depends on the project size. If the project is 1GB, it downloads 1GB everytime you build it.
Clean before checkout removes the files created as part of build - say your test results etc - resets the files if they were updated & pulls the latest changes if they have been updated. This ensures that the workspace is in the same state as if you cloned and checked out in a brand-new empty directory. It downloads only the delta which could be few MBs. So it is less time consuming.
So you can go ahead use Clean before checkout without affecting the build.
Have been using this option for more than 4 years without any issues.
