如何使用IBM Bluemix Track& amp;管理多个组件计划 [英] How to manage multiple components with IBM Bluemix Track & Plan

问题描述

我们有一个包含多个不同组件（不同功能/语言）的应用程序。

We have an application that is comprised of multiple distinct components (different functions / languages).

在IBM Bluemix中是否可以使用单个Track& ;？计划功能来管理组件的工作项，但将源代码保存在单独的git存储库中？例如，我想为整个应用程序准备一份积压订单，然后由5个单独的git repos作为后备订单，其中包含各个组件（项目前端，项目后端，项目队列等）。

Is it possible in IBM Bluemix to use a single Track & Plan feature to manage the work items for the components but keep the source code in separate git repositories? For example, I would like to have one backlog for the overall application which is then backed by 5 separate git repos which house the individual components (project-frontend, project-backend, project-queue etc..).

如果这不可能，那么有人是否有一种模式可以简化整个Track&规划并仍启用交付管道/管理单个git仓库？理想情况下，我想集中化任务管理，但要保持代码的分布式。

If this is not possible does anybody have a pattern that has worked in streamlining the overall Track & Plan and still enabling the delivery pipeline / managing individual git repos? Ideally I'd like to centralize task management but keep the code distributed.

推荐答案

到目前为止，还没有办法从单个 Track&管理分布式git存储库以集成方式计划项目。这并不是说它不能手动完成，而是需要链接到给定工作项中远程存储库中的提交。

As of now, there is not a way to manage distributed git repos from a single Track & Plan project in an integrated fashion. That is not to say that it cannot be done manually, but you would need to link to commits in the remote repos in a given work item.

这可以通过以下方式完成：给定工作项目的链接标签，并使用添加SVN修订版本或添加相关工件。这将允许您链接到远程存储库（无论是在IDS，GitHub还是专用SCM工具中），同时仍可利用 Track&计划作为总体计划仓库。

This can be done through the Links tab of any given work item and using the Add SVN Revisions or Add Related Artifacts. This would allow you to link to the remote repos (whether in IDS, GitHub, or private SCM tooling), while still leveraging Track & Plan as an overall planning repo.

部分原因是由于今天在 IBM Bluemix DevOps Services 中构建项目的方式。单个项目具有单个git repo，单个Track&计划实例和一个构建管道。其中一些需求正在不断扩大，但是该平台提供了集成功能，可以以您现在需要的方式与您的代码一起使用。例如，项目所有者可以从项目的Build Pipeline中的远程GitHub仓库中进行构建，以便可以按需管理代码，但可以在 IBM Bluemix 上构建和部署代码。

Some of this is due to the way projects are constructed in IBM Bluemix DevOps Services today. A single project has the notion of a single git repo, a single Track & Plan instance, and a single Build Pipeline. Some of these requirements are expanding, but the platform provides integration capabilities to work with your code the way you need to right now. For example, project owners can build from remote GitHub repos in the project's Build Pipeline, so that code can be managed as you see fit, but built and deployed on IBM Bluemix.

这篇关于如何使用IBM Bluemix Track& amp;管理多个组件计划的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！