If you have never used a source code management and versioning system like ClearCase or Subversion before, perhaps you feel a tangible comfort in being able to start SEU on a source member to see what's there. Perhaps you find the thought of storing all your source in some other repository a bit unnerving.
Fear not RTCi.
With RTCi, the source you're managing is being stored in that very same database on IBM i that you trust to manage your source members today... with a major difference: it's versioned. Imagine audit journalling turned up to the max, stored more efficiently.
Today, you can only see the current contents of the source member. With RTCi, you can see the whole history of changes. For each change, you can see what lines of code were changed, who changed them, when it was changed, why it was changed, and where it was compiled.
Imagine being able to rollback source changes that introduced a bug, or suspend the changes you're making on some enhancement, to work on some emergency fix for production code. Imagine having a problem reported by Quality Assurance for the changes you delivered last Friday, and being able to reconstruct the exact state of all the code that you delivered to QA at that time, so that you can debug the problem.
RTCi Team Blog
Previous Next
Nazmin
in response to: ALSWizard
I don't understand the question. If you are looking at the Pending changes view and see incoming changes, then this means that the iProject that you have locally on your PC (in your local workspace) and is shared in Jazz Team Server for i, was changed by a team member(s). By accepting the changes, you will update the iProject on your PC with these changes - meaning that the contents of the iProject that you have locally will match what's in the Team Stream on the Jazz Team Server for i. This has nothing to do with what's in your library on IBM i.
ALSWizard
in response to: Nazmin
Thanks for clarifying that relationship. As for what needs to be backed up given what you just wrote, is my understanding correct (as follows) given my setup? I am both the administrator and one of the developers for the project. I have two separate userIds and two separate RDi workspaces on the same PC. As the administrator, once I "Accept All Incoming Baselines and Change Sets", is it the administrator's RDi workspace that has just been updated and should therefore be backed up? Or per the "Backup before replace" task, to backup the administrator's workspace first?
Nazmin
in response to: ALSWizard
What are you trying to backup? Once you have your source in Jazz Team Server for i, the master copy of the source should be kept there. As an administrator or the developer you update the source locally on your PC and deliver it to the Jazz Team Server for i. The repository is on IBM i where the Jazz Team Server for i is running. It is indeed a library (schema) that you specified in the teamserver.properties file when setting up the server on IBMi. You can backup this library using the Repository Tools Application (aka repotools) which is installed as part of the server installation under repository directory. You can find more information on this on jazz.net. If you have installed RDi and selected RTCi as an optional install, you can search for repotools in the help as well.
Pending Changes "Backup before replace". I am new to Concert for i and I can't determine if I'm being told that I must make a backup of my library before I "Accept All Incoming Baselines and Change Sets" OR if Concert will do it for me. I've searched all the help I can find and I don't see anything about it. Any suggestions?