Do you have an existing IBM Rational Team Concert server that you use for tracking and planning? You can now integrate this server in IBM Bluemix Continuous Delivery. This Rational Team Concert integration not only adds a card to your toolchain for quick access to your work items, it also adds tags to the work items that have been deployed. Such tags allow you to run powerful queries for tracking deployment of code changes as well as build useful Rational Team Concert dashboards.
The steps below explain how to enable the Git integration in Rational Team Concert to automatically create links to Git commits in Rational Team Concert work items.
Configure Rational Team Concert integration
As for other tool integrations, you can add Rational Team Concert integration to your toolchain by:
Pressing the Add a Tool button
Selecting Rational Team Concert in the list of available tools
Configuring the integration
Check Track deployment of code changes to track your code changes using Rational Team Concert dashboards.
After you pressed the Create Integration button, you get a new card added to your toolchain. This card is linked to the Rational Team Concert project that you want to use for tracking and planning.
Configure a Git integration in Rational Team Concert
This step is optional. It allows you to have links to the Git commits automatically added in the Links view of the Rational Team Concert work item when the Git commit comment references this work item. Such comments would look like: “task 7244”.
Track your code changes using Rational Team Concert dashboards
Assuming you have checked Track deployment of code changes while configuring the Rational Team Concert integration, and that you referenced a work item in the Git commit comment, a successful deploy of your application will create a tag (e.g., deploy:prod) in the Rational Team Concert work item as well as a comment indicating that the work item is deployed.
Thanks to the generated tag, you can now create a dashboard to track work items that have been deployed, work items that are closed but not deployed, what environments work items are deployed in, etc.
When I look back at that school project, it would have been easier and more effective if we had used DevOps toolchains in IBM Bluemix Continuous Delivery. In a toolchain, we could have stored and managed the code in one place, provided all my team members access to the information they needed, tracked issues, and debugged and tested efficiently. I would have learned more about continuous integration and delivery. Moreover, the project would have come together easily because of the integration with the cloud.
Well, what if you could develop applications running on Bluemix incrementally? What if, the minute you save a file, your code is deployed to your running Bluemix app instance, enabling a wonderfully efficient code-test cycle? Bluemix Live Sync lets you do just that!
Almost a year ago, when we first announced and released IBM Globalization Pipeline on Bluemix, we were looking to solve a simple problem facing Bluemix development teams wanting to expand into global markets -- how can Cloud dev teams translate their applications into different languages without impeding continuous delivery and disrupting DevOps?
In answer, we delivered Globalization Pipeline -- a Bluemix service that enables developers to integrate translation processes into their build and deploy infrastructure and translate their apps using machine translation. Think integration with IBM DevOps services, UrbanCode Deploy, Continuous Delivery, Maven, VS Code, and Atom, think Watson Language Translator, think client SDKs for dynamic app translation updates.