I have recently announced we are working on Dependency Based build for Git but we already have the capability in Rational Team Concert (RTC) and you are either already using it or looking at it. First I want to assure you we are continuing our support of RTC for z/OS development. It’s a critical capability for many of our clients and for us internally and provides something Git won’t. RTC provides the fully inte
RTC’s SCM is a full function centralized SCM. It supports multiplatform development, so you can move many of your teams into RTC. Along with the SCM it provides a fully integrated buil
So why are we doing Git support, some organizations have selected GIT as their enterprise SCM, for it’s open sharing nature, or as many organizations say because it’s what the developers are asking for. When Git is your enterprise SCM we want to make sure your z/OS source code can be part of the solution, and not separate. We want to make sure z/OS is a first class supported platform in any corporate DevOps transformation and if what it takes to do that is to support GIT. Then we will.
There is another reason to do Git support, and that is choice. Today RTC is the only modern SCM that fully supports z/OS artifacts as well as distributed. No other vendor has invested in building an SCM that supports all platforms. Other solutions that support z/OS artifacts are only for z/OS artifacts, they don’t support multiple platforms and don’t provide a fully functioning SCM. It’s somewhat funny that the only other SCM like solution developed in the last 30 years for z/OS artifacts requires a modern SCM in front of it if you want to do Java because it does not have the function the distributed teams are asking for. If the SCM does not have the function the distributed teams need, it does not have the function required by any developer. It’s this need for choice that has had us push for Git support. If your doing z/OS development you should be able to use just as modern a solution, and you should not be locked away in an solution that does not participate with other platforms.
Which is right for you, that’s going to depend on a number of factors, but since RTC is a single integrated tool for SCM, Build, Work items, Planning and Dashboards, and Git is only and SCM we are going to focus this comparison on only the SCM capabilities. This is a partial list, but contains some of the key characteristics I have heard used for selection.
- centralized SCM
- security to control access to code based on project, team, or components
- users can load only the files they want to
- process controls to enforce rules before check in
- direct linkages to what build includes which changes
- direct integration to load files into PDSEs or PDSs as well as the zFS
- full code page support
- meta data addable to the managed artifacts that is also versionable
- streams and workspaces for parallel development with merging
- distributed SCM
- every user has a full copy of the repository on his or her laptop or system they are working on along with the history allow fully independent work
- integrated with zFS on z/OS
- code page support when running on z/OS with the Rocket port
- git hooks available for process controls
- file tagging support
- simple to use branching for parallel deve
lopm ent with mer ging
- ability to remove changes after committed
It is important to recognize that you can use RTC for planning and management as well as your dashboarding to have the integrated solution and still use Git as your SCM. RTC provides the git hooks to have the linkage with RTC work items associated with the git changes as they are committed or pushed based on the git commit. It may be that both are right for you, for projects you want to work more like open source projects use git, for gold or jewel code use RTC to control the access.
So which is right for you and your company will be dependent on your strategy, but now you have a choice. It's time to move to take advantage of the modern capabilities.
Rosalind Radcliffe is a Distinguished Engineer within the IBM Rational organization. She is Chief Architect for CLM and DevOps. She is responsible for driving the DevOps for multi-platform architecture. This includes System z and Power system. In addition, she is responsible for the architecture for the Collaborative Management capability for Enterprise solutions. This includes UrbanCode Deploy and Rational Team Concert's support for standard Mainframe development activities. She is a member of the IBM Academy of Technology and a Master Inventor. Prior to Rational, she was in Tivoli responsible for the SOA Management Strategy for IBM.