It has been a while since my last post. It hasn’t been because of lack of ideas, rather time, although the blog has been bugging me in the back of my mind for attention for quite some time. So here we go … for this come back I have picked an always interesting topic, to force some rules in your SCM.
I wanted to talk about one aspect of managing change sets in Rational Team Concert. Tools like RTC and Rational Developer for z Systems come in hand with the cultural and practices changes in the umbrella of Enterprise Modernization, but let’s face it, there are certain challenges that come into play in discussions with customers quite commonly and will take some time to leave … if ever (languages used and platform peculiarities play their part as well).
In (specially) mainframe development environment, there are situations in which duplicate element names can be problematic. And from time to time I get helping customers migrate to Rational Team Concert, I find them asking of a way of ensuring this source elements names uniqueness in SCM can be enforced. In this post I am going to show an advisor for such enforcement, and talk about some restrictions to the approach.
I have recently been working on writing a custom service to automate some computed information retrieval from an RTC Server. That service I wanted it to have a configuration property that could be set/modified using the Advanced Properties page (https://<yourServerURI>/ccm/admin). In that process I faced a “dummy” issue that made me waste some precious time, so I wanted to share here my experience.
This post is meant to be a really short one, with the idea of providing a tip based on my experience.
Note: if this a kind of custom element you may need in your deployment but you don’t know where to start, I advice you to firstly take a look at Hello Jazz — How to write a simple Jazz component at jazz.net.
Work Item based Promotion allows you to move your changes related to a certain work item in your streams hierarchy. At the same time, Rational Team Concert allows a great flexibility to “move” your changes between work items, so developers can report their work or decide which changes better represent their tasks work. However, when it comes to work items promotion, there are times where this flexibility can lead you to undesired scenarios.
Back from Innovate, it has been a great time meeting lots of Jazz practitioners and buddies; most of them it was the very first time I was meeting in person, after long time working together. After the usual time for catching up with tasks that were waiting for me, I am back to my blog. I have been recently working in an engagement helping building a custom asynchronous scheduled task, so I wanted to write about it.
I have had some difficult time trying to find an example of such a task that was both simple enough and yet close to a real case; so finally instead of complicating myself, I decided to use as basis the example from the Query Dev Guide wiki page with some little modifications, but with focus on the details of building such an async task.
I have been recently working on extending the Rational Team Concert Bugzilla Importer functionality and I wanted to take some time to blog about it. Rational Team Concert provides an Import wizard to migrate Bugzilla Bug Reports to RTC. The details of such feature are described in this jazz.net article and this InfoCenter topic.
Update Feb 11 2013: I have updated the shared code to be able to ignore the Bugzilla bugs’ attachments.
The post content is the original one but you will find in the wizard the option to ignore the import of attachments, which may be useful when you are migrating old bugs information for traceability but you don’t want to carry all the attached files to your RTC database.
From some time ago I wanted to post a chunk of code to enable to launch a build as a result of a deliver operation. I have found myself in some situations in which this kind of automation has been asked, and I wanted to play a bit wit the SCM part of RTC SDK, so in this post I want to publish some code sample that I hope will be useful for people having this or a similar need.