识别构建工件的确切组件版本
如何为相当复杂的产品设置基于 Jenkins 的构建流程(使用 Artifactory Pro 进行工件存储),以便可以轻松识别其每个组件的版本/修订版?
其中一些组件可能是从其他组件创建的(本质上是聚合),因此需要依次识别这些子组件修订版。
我不想一直构建完整的(大型)产品,将其源代码一起存档,而是使用以前创建的工件。在开发过程中,他们可能会有一个使用一段时间的快照版本。
当在测试过程中发现问题时,如何将其追溯到每个已完成产品组件的确切源代码控制修订版本以进行分析? 我们不会在所有事情上使用 SVN,并且其他 VCS 也没有 Jenkins 插件。
我们所做的一些工作是基于 Maven,但解决方案应该足够灵活,不需要 Jenkins 中的 Maven 项目。
How can I set up a Jenkins based build process (using Artifactory Pro for artifact storage) of a fairly complex product so that the version/revision of each of its components can be easily identified?
Some of these components might have been created from other components (essentially, an aggregation), so those sub-component revisions would need to be identifiable in turn.
I'd rather not build and the complete (large) product all the time, archiving its sources along with it, instead using previously created artifacts. During development, they'd likely have a SNAPSHOT version that is used for a while.
When, during testing, an issue is discovered, how can I trace it back to the exact source control revisions of each of the completed product's components for analysis? We don't use SVN for everything, and there's no Jenkins plugin for the other VCS.
Some of what we do is based on Maven, but solutions should be flexible enough to not require a Maven project in Jenkins.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您可以使用 maven-buildnumber-plugin 从 Subversion 获取修订号并放入将此信息写入 MANIFEST 文件中。
如果不存在 SVN 工作副本,以下代码片段将调用 buildNumber 插件并使用不同的版本字符串。可能可以用jenkins等的Job_ID替换。
You can use the maven-buildnumber-plugin to get the revision number from Subversion and put this information into the MANIFEST file.
The following snippet will call the buildNumber plugin and use a different string for the version if no SVN working copy exists. May be this can be replaced by the Job_ID of jenkins etc.