与Jenkins的持续集成-澄清 [英] Continuous Integration with Jenkins - clarifications
问题描述
我们正计划与Jenkins软件实现持续集成，因此我们已在服务器(Windows平台)中成功安装了Jenkins
We are planning to implement continuous integration with Jenkins software, so we successfully installed Jenkins in our server (windows platform)
我的问题是
-
如何管理(保留)我的源代码?
How can I manage (keep) my source code?
我们如何配置源代码是否位于其他计算机/服务器/云
How can we configure if the source code located in some other machine / server / cloud
我们当前的过程
Jenkins，源代码可在同一台计算机上使用，因此我们在Jenkins中创建了一个项目，并将pom.xml(如D:\ pom.xml)文件映射到build部分.
Jenkins, source code is available in same machine, so we created a project in Jenkins and map the pom.xml (like D:\pom.xml) file under build section.
推荐答案
选择一个版本控制工具，请考虑SVN和GIT完全不同(Git->分布式系统，SVN->集中式系统)，因此请阅读有关请先选择它们，然后检查Jenkins中GIT/SVN插件的可用性，除非您的Jenkins安装中已包含该插件.
Choose a Version control tool, consider that SVN and GIT are quite different (Git--> Distributed system, SVN-> Centralized system) so read a bit about them before choose, then check for the availability of GIT/SVN plugin in Jenkins unless it already contained in your Jenkins installation.
将代码置于SVN/GIT下，遵循标准，配置Jenkins以便访问SVN/GIT服务器.
Put the code under SVN/GIT, follow the standards, configure Jenkins in order to access to SVN/GIT server.
检查如何使用Jenkins配置Maven，它与Maven集成得很好.
Check how to configure maven with Jenkins, it has a great integration with Maven.
Maven Jenkins: https://www.tutorialspoint.com/jenkins/jenkins_maven_setup.htm
Maven Jenkins: https://www.tutorialspoint.com/jenkins/jenkins_maven_setup.htm
Jenkins Git: Jenkins和Git稀疏签出
Jenkins Git: Jenkins and Git sparse checkouts
单个构建作业的流程为:
The flow of the single build job is:
- 结帐代码
- 使用pom.xml文件指定文件夹
- 运行所需的Maven目标(例如mvn install)
这篇关于与Jenkins的持续集成-澄清的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
