Hudson 下游项目未列出上游依赖项
我有一个上游项目（dao）和一个下游消费者（scb）。我想对其进行配置，以便在构建 scb 时，构建摘要页面（单击构建号后）将显示“上游构建：dao #blah”。
我该怎么做？看看这个问题，我已经配置了scb到：
- 每当构建 SNAPSHOT 依赖项时构建
- 构建其他项目后构建 (dao)
我还配置了 dao 项目以通过“构建其他项目”进行构建，尽管理想情况下，我不想触发构建；我只是想让 scb 向我展示它用作上游项目的 dao 版本。
如果有帮助的话，这些都是 Spring/Hibernate Java 项目，每个项目都构建一个 JAR 文件； dao 项目是一组常见的 DAO 类。
为了清楚地说明我在说什么，Hudson 有一个项目关系链接。此链接用于显示某些 dao 版本和某些 scb 版本之间的联系。 （我希望它能为所有新版本执行此操作，但它停止了。）我希望填充这些数据。 （我认为这与构建版本屏幕中显示的上游/下游相同。）
I have an upstream project (dao) and a downstream consumer (scb). I would like to configure it so that when scb is built, the build summary page (after clicking on a build number) will show "Upstream builds: dao #blah".
How do I do this? Looking at this question, I already have scb configured to:
- Build whenever a SNAPSHOT dependency is built
- Build after other projects are built (dao)
I also have the dao project configured to build via "Build other projects," although ideally, I don't want to trigger the build; I just want scb to show me which build of dao it used as an upstream project.
If it helps, these are both Spring/Hibernate Java projects that each build a single JAR file; the dao project is a group of common DAO classes.
To be clear what I'm talking about, Hudson has a project relationship link. This link used to show a connection between certain builds of dao and certain builds of scb. (I wish it would do that for all the new builds, but it stopped.) I want this data to be populated. (I presume this is the same as showing upstream/downstream in the build-version screen.)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
好问题。成立
在 操作系统目录邮件列表
Good Question. Found
On OS Dir MailingList
请参阅您在问题中引用的同一问题。为 **每当构建快照依赖项时构建 和 viola 配置构建触发器*部分。
此外，下游构建完成并成功也很重要。失败或测试失败的构建将不会触发下游构建。
我知道您已经看到它们已经出现在您的系统上，但这非常奇怪。
See the same question you referenced in your question. Configure the Build Trigger* section for **Build whenever a SNAPSHOT dependency is built, and viola.
Also, it's critical that the down-stream builds complete and are successful. Builds that fail or failed tests will not trigger downstream builds.
I know you've seen that they have on your system, but that's downright strange.