简体   繁体   English

Jenkins部署需要很长时间才能从SVN检出代码以获取新标签

[英]Jenkins Deployment Takes Long Time to Checkout Code from SVN for New Tags

Using Jenkins as CI for Deployment on the Linux Server. 使用Jenkins作为CI在Linux服务器上进行部署。 The Deployment is Easy and Convenient. 部署既简单又方便。

But the Problem is, Each time if i need to Deploy the build to Newly Created SVN Tags , The SVN checkout takes Long Time. 但是问题是,每当我需要将构建部署到创建的SVN标签时 ,SVN结帐就需要很长时间。 The Checkout of .jar files is taking long time. .jar文件的检出需要很长时间。

Is there any way to Skip this part? 有什么办法可以跳过这一部分吗? I mean, Manual Copying of .jars (something like this) will help in overcoming the Deployment Time? 我的意思是, .jars的手动复制(类似这样)将有助于克服部署时间? or Any other Procedure? 或其他程序?

In my opinion, Jar files should not be version controlled in source control system but instead their source code alone should be version controlled in SVN. 我认为,Jar文件不应在源代码管理系统中进行版本控制,而应仅在SVN中对它们的源代码进行版本控制。

However, if you have it setup the jar files in SVN, then I would suggest you move them to a common folder in SVN like library and then do a checkout only when there is a change to the library folder. 但是,如果您用它在SVN中设置了jar文件,那么我建议您将它们移到SVN中的库(例如库)中,然后仅在库文件夹发生更改时进行签出。

In the Jenkin's job workspace, the libraries can be referred relative to the Job workspace directory / a separate job can be configured to update/ checkout the libraries on a need basis. 在Jenkin的作业工作区中,可以相对于作业工作区目录来引用库,也可以配置单独的作业以根据需要更新/签出库。

This will help reduce the latency of your actual job wasting time in pulling down libraries from SVN. 这将有助于减少从SVN中删除库时实际工作浪费时间的延迟。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM