简体   繁体   English

一个用于两个不同jenkins构建的svn项目(具有另一个依赖项)

[英]one svn project for two different jenkins builds (with another dependency)

Following scenario: Existing Jenkins project (called A) with a dependency (3D extension) with a SVN connection. 遵循的场景:现有的具有SVN连接的依赖项(3D扩展)的Jenkins项目(称为A)。 This dependency is also a Jenkins project also with a separate SVN connection. 此依赖项也是Jenkins项目,也具有单独的SVN连接。

What I want to do now: 我现在想做什么:

Create another Jenkins project as reference of A w/o the 3D extension (called project B). 创建另一个Jenkins项目作为A的参考(不包含3D扩展)(称为项目B)。 It's absolutely necessary that I haven't got to copy project A in it's full source code / SVN. 绝对没有必要使用完整的源代码/ SVN复制项目A。 Jenkins mustn't throw error for the project B, because it can't find the 3D extension. 詹金斯(Jenkins)一定不要为项目B抛出错误,因为它找不到3D扩展名。

What do I have to do now? 我现在该怎么办?

I have thought of creating another POM file and use it as parent POM for project B. This POM doesn't include the 3D extension, but listens on the SVN connection of project A. 我已经考虑过创建另一个POM文件,并将其用作项目B的父POM。此POM不包括3D扩展名,但侦听项目A的SVN连接。

The project A with 3D extension is the child POM, which uses the parent POM and additionally the 3D extension. 具有3D扩展名的项目A是子POM,它使用父POM以及3D扩展名。

Is it the right approach? 这是正确的方法吗? What I didn't understand is, how Jenkins could avoid the compiling error when compiling "project B", because of the missing 3d extension. 我不明白的是,由于缺少3d扩展,Jenkins如何在编译“项目B”时避免出现编译错误。

为您提供的解决方案是参数化的构建脚本

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

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