How to manage multiple components with IBM Bluemix Track & Plan

Question

We have an application consisting of several separate components (different functions / languages).

Is it possible that IBM Bluemix uses one Track and Plan feature to manage work items for components, but save the source code in separate git repositories? For example, I would like to have one backlog for a common application, which is then supported by 5 separate git repositories that host the individual components (project interface, project backend, project queue, etc.).

If this is not possible, does anyone have a template that worked to streamline the common track and plan and still allow the delivery / management pipeline of individual git repositories? Ideally, I would like to centralize task management, but retained the code.

Answer 1

There is currently no way to manage distributed git repositories from one Track and Plan project in an integrated way. This does not mean that this cannot be done manually, but you will need to link to the commits in the remote repositories in this work item.

This can be done using the Links tab of any given work item and using Add SVN Revisions or Add similar artifacts . This will allow you to connect to remote repositories (whether in IDS, GitHub or a private SCM tool), but use Track and Plan as a general repo planning.

Some of this has to do with how projects are created in IBM Bluemix DevOps Services today. In one project, there is the concept of one git repository, one instance of Track and Plan and one assembly pipeline. Some of these requirements are expanding, but the platform provides integration capabilities for working with your code as you need right now. For example, project owners can build from remote GitHub repositories in a Build Pipeline project, so the code can be managed as they like, but it is embedded and deployed on IBM Bluemix.