Jira/GreenHopper 中组件的有效版本控制？
是否有对项目组件进行版本控制的最佳实践或推荐方法？只是我可能有一个 EnvironmentServices 项目，其中包含组件 SpecificService1、SpecificService2...每个子组件都有独立的版本控制。
实现这一目标最有效的方法是什么？由于独立的 Jira 似乎不支持组件版本控制：如此处提出的。
为每个我希望有生命周期的“SpecificService”创建项目？或者我可以利用 GreenHopper 并使用组件/版本层次结构吗？
任何建议表示赞赏。
Is there a best practise or recommended method of versioning components of a project? Just I may have an EnvironmentServices project with components SpecificService1, SpecificService2... each of these children have independent versioning.
What is the most effective method of implementing this? As standalone Jira doesn't seem to support component versioning: as raised here.
Would it be to create projects for each 'SpecificService' I wish to have a lifecyle for? Or can I take advantage of GreenHopper and use Component/Version hierarchies?
Any suggestions are appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我们的公司就是这样，在尝试了 Greenhopper 的东西之后，我们回到了显而易见的答案：命名约定。
举个例子，假设我们有一个项目，用于一些紧密集成的代码库，其中包括 REST 服务和管理 Web 应用程序。然后我们就有了组件“Service”和“WebApp”。然后我们创建名为“Service 1.2.0”和“WebApp 2.1.1”的版本。这使得我们可以在两个版本中都存在适用于两个组件的错误。
它不会强制执行任何内容，但浏览系统的任何人都非常清楚交易是什么，而且人们很快就会明白。
We have this as our company, and after trying the Greenhopper stuff, we went back to the obvious answer: naming conventions.
As an example, say we have a single project for some tightly integrated codebases which include REST Service and an administration WebApp. We then have the components "Service" and "WebApp". Then we create versions called "Service 1.2.0" and "WebApp 2.1.1". This allows us to have bugs which apply to both components to be in both versions.
It doesn't enforce anything, but it is really clear to anyone browsing the system what the deal is, and people catch on quickly.
我开发了一个 JIRA 插件，可以实现组件级版本控制。它适合您所描述的具体场景。除了组件特定版本之外，您还可以将不同的组件版本分组到一个捆绑包中。您可以从 Atlassian Marketplace 或 插件的帮助页面。
I have developed a JIRA plugin that makes component level versioning possible. It is suitable for the exact scenario you have described. In addition to component specific versions, you can also group different component version into a bundle. You can check plugin details from the Atlassian Marketplace or plugin's help pages.