简体   繁体   English

Jira / Subversion / CruiseControl发行说明,迁移到Bamboo?

[英]Jira/Subversion/CruiseControl release notes, migrate to bamboo?

We are using a combination of Jira, Subversion and CruiseControl.net in our workflow. 我们在工作流程中结合使用了Jira,Subversion和CruiseControl.net。 With each commit, the corresponding Issue-ID is stored in a bugtraq-property of svn. 每次提交时,相应的Issue-ID将存储在svn的bugtraq属性中。 Jira accesses the repository via plugin (not FishEye at the moment), and a custom svn hook updates the Jira-Issue with the branch name. Jira通过插件(当前不是FishEye)访问存储库,并且自定义svn挂钩使用分支名称更新了Jira-Issue。 So each issue is linked to all branches it relates to. 因此,每个问题都链接到与其相关的所有分支。 Also, release notes for each issue are stored in custom fields, as we need the release notes in multiple languages. 另外,每个问题的发行说明都存储在自定义字段中,因为我们需要多种语言的发行说明。 CruiseControl runs builds on schedule, with increasingly complex build scripts to integrate the release notes into our application. CruiseControl按计划运行构建,并使用越来越复杂的构建脚本将发行说明集成到我们的应用程序中。 As some of the branches are custom userware, only a subset of the release notes are actually used (requirements of one customer should not neccessarily be visible to other customers, whereas the customer information is generated from the branch names). 由于某些分支机构是自定义用户软件,因此实际上仅使用发行说明的子集(一个客户的需求对于其他客户而言不一定是可见的,而客户信息是从分支机构名称生成的)。 I've spent quite some time on the web looking for plugins to interface Jira and CruiseControl with eachother to better automate this process. 我已经在网络上花费了很多时间来寻找用于相互连接Jira和CruiseControl的插件,以更好地实现此过程的自动化。 Is there anyone out there with similar problems? 有没有人遇到类似的问题?

Would a migration to Jira/Bamboo/FishEye solve my problem? 迁移到Jira / Bamboo / FishEye是否可以解决我的问题? I've downloaded the test versions and dabbled around with the tool integration, but I'm really looking for constructive advice and experience reports. 我已经下载了测试版本并涉足工具集成,但是我确实在寻找建设性的建议和经验报告。 The ability to start builds from within Jira certainly looks appealing, and FishEye should provide branch information to Bamboo. 从Jira内部开始构建的能力确实吸引人,并且FishEye应该向Bamboo提供分支信息。 I hope, I'm making sense here... Thanks in advance. 希望我在这里有意义...预先感谢。

Jira and Bamboo are obviously better integrated. 吉拉(Jira)和竹(Bamboo)显然整合得更好。 SVN hooks to Jira are better than Fisheye smart commits. SVN挂钩Jira优于Fisheye智能提交。 The only other CI product with this level of integration with Jira is Jenkins via marvelution plugin: https://marketplace.atlassian.com/plugins/com.marvelution.jira.plugins.jenkins 与Jira进行此级别集成的唯一其他CI产品是通过marvelution插件进行的Jenkins: https ://marketplace.atlassian.com/plugins/com.marvelution.jira.plugins.jenkins

Our shop is a lot of Java developers, a few MS devs. 我们的商店有很多Java开发人员,还有一些MS开发人员。 Java developers mainly use a SVN/Jira/Fisheye/Jenkins combo with release notes generated automatically via Jira and Jenkins. Java开发人员主要使用SVN / Jira / Fisheye / Jenkins组合以及通过Jira和Jenkins自动生成的发行说明。 The MS developers use TFS for their projects. MS开发人员将TFS用于他们的项目。

You could always bite the Microsoft bullet and use TFS 2012. 您总是可以咬Microsoft子弹并使用TFS 2012。

So besides the ITIL-breaking release management snieps in the question comemnts, the answer is Jira/(Jenkins|Bamboo) will solve your problem. 因此,除了在问题中破坏ITIL的发布管理功能外,答案是Jira /(Jenkins | Bamboo)将解决您的问题。 Fisheye is just a nice to have. 鱼眼真是太好了。

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

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