version control

Arthur Adams's picture

What are the current IBM/Rational offerings?

Arthur Adams asked on August 24, 2017 - 8:11am | Replies (0).

I've used Ratiional ClearCase and ClearQuest in the past, but it's been a long time - at least seven years since I used CQ, and probably a decade since I used CC. On a project where we used both, I had them integrated. (I used them enough to refer to them collectively as "ClearWaste".)

I'm currently tasked with evaluating various CM-related suites for where I'm working now, and I'm finding it very confusing to determine just what IBM is currently offering.

I see ClearCase and ClearQuest are still sold. Are they actively supported?

<em>No answers yet</em>

Arthur Adams's picture

What are the current IBM/Rational offerings?

Arthur Adams asked on August 24, 2017 - 8:10am | Replies (0).

I've used Ratiional ClearCase and ClearQuest in the past, but it's been a long time - at least seven years since I used CQ, and probably a decade since I used CC. On a project where we used both, I had them integrated. (I used them enough to refer to them collectively as "ClearWaste".)

I'm currently tasked with evaluating various CM-related suites for where I'm working now, and I'm finding it very confusing to determine just what IBM is currently offering.

I see ClearCase and ClearQuest are still sold. Are they actively supported?

<em>No answers yet</em>

Saravanan Ganapathy's picture

CA SCM Harvest Workbench E0306003e: Could not connect to Broker

In CA SCM Harvest Workbench, Version 12. 1..1.141 We face below error while check our or promoted. not always but frequently. what should be done to overcome this issue ? I tried to reinstall PEC in user maching, but it didnt fix. Any solutions ??

E0306003e: Could not connect to Broker: /pt_HBroker://r62dp10/0/haprd5 (Error Code = -307)

<em>No answers yet</em>

sundarrajan rangarajan's picture

Failed to connect dimensions server

Hi,

Trying to connect to dimensions (10.1) thru desktop client, it throws "Failed to connect to the dimensions Server"  error

 

The trace log is give below

$ cat DMPOOL_root_3014772_20170202T093401.log

DMPOOL 2017/02/02 09:34:01 I P3014772 T1 -service pcms_sdp -user dmsys -dsn [email protected] -min 5 -max 120 -initial 5 -free 5 -idle_timeout 300 -session_timeout 3600 -tracedir /dimensions/10.1/cm/dfs/trace.20150929 -trace

DMPOOL 2017/02/02 09:34:01 T P3014772 T515 bind to port 671, attempt 1

<em>No answers yet</em>

Sithik Settu Mohamed's picture

Remove mercurial subrepos and move it to main repository. Please suggest the good way to perform the same?

Am working in a old project which has many hg subrepos which seems to be problematic. Am planning to remove subrepos and move to main repository. Is there any better approach to do the same or any tools? Also want to maintain the same metadata and not interested to add all subrepo as single commit to main repository.

<em>No answers yet</em>

Sameer Deshmukh's picture

Exclamation status "A comment is required to check in object(s)" while sync projects in Rational Synergy version 7.2

Project is 1.3 Gig and sync times out with status "A comment is required to check in object(s)"

<em>No answers yet</em>

[article]

Use Version Control to Unlock Your Development Velocity

Summary:

Effective source code management provides a basis for every essential development best practice, including continuous integration and continuous delivery. The key is realizing just how much valuable metadata is being created in your source code management system and establishing the tools and procedures to make this information available.

Effective source code management provides a basis for every essential development best practice, including continuous integration and continuous delivery. The key is realizing just how much valuable metadata is being created in your source code management system and establishing the tools and procedures to make this information available.

About the author

Robert Martin's picture

Does anyone have any experience using Service Now as a version control tool? Pros/Cons?

Have heard Service Now is a good Help Desk type tool for tracking incidents.  Can it's tool suite be used effectively in an IT development environment for version control, baselines, releases/deployments, etc.

Drew Benson's picture

As per above - ServiceNow is an (ITIL based) Service Management Tool.

Arguably a pretty decent one. But it has no functionality (or even the concept) of software/file version management.

Its various process records can have (file) attachments etc (and complex process driven interactions).

It could be customised to have pretty good process control over your development process and it could support your Version Management (SCM) process and even possibly have links into VM tools (all or most of the usual suspects).

 

 

 

 

Thomas Loy's picture

I've used Service Now in the past, but I really don't think it would be a good tool for version control or baselines.  Git or Subversion or other VC softwware would be your better choice for version control and baselines.  Other tools would also probably be better suited for releases and deployments.  I don't think Service Now has capabilities for any of that.  However, Service Now might be good for documenting and tracking information about versions, baselines, releases and deployments, especially if you can use the tools APIs so they can communicate with each other when things happen, such as commits, pulls, and deployments.  It would be a good place for capturing the who, what, when, where, how and why.  

Deepak KS's picture

How do we use Stash/Bit Bucket Server for our product development?

Deepak KS asked on February 1, 2016 - 10:40pm | Replies (1).

Dear Experts,

Need your expter advice in setting up a new repository structure for our product development.

We have a software product, with 15-compnents and each of the 15-components have at least 15-modules.

Earlier our admin guy had configured the Stash server for us.

The current setup is like this:
Our IT engineer had created 15-Projects in stash/bitbucket server for 15-Components
For each of the 15-modules in a given component, a individual repository was created

Bob Aiello's picture
Bob Aiello replied on February 14, 2016 - 6:46pm.

The pattern as you described is indeed how I see folks using Bitbucket (formerly called Stash).
Keep in mind that you can easily pull every repo at once from the commandline so this organization is pretty easy to work with.

Bob Aiello, Technical Editor

Johan Sundqvist's picture

Best practice for changes to source code that are part of a solution to resolve two different Product Change Requests?

In practice I have two new features that are under change control and that I want to be able to track them as separate changes from the first change and until the features are deployed to production.
 
How do I handle the fact that they both need to make the same changes to one part of the code? If I let one of them carry the change but then decides later on to back out of that “Feature” then I  will break the other feature that where depending on the same change. 
 

Johan Sundqvist's picture

Thanks again Drew for taking time to answer my questions in detail.

Best regards!

 

/johan

Drew Benson's picture

I don't want to get too hung up on process detail here (what "boards" you have/need what you call them etc etc) as we are only looking at a tiny snapshot but I would expect a bit more sanity within your process than "formal" approval at such a granular level ............

The "work" (and business need etc) for Feature A and Feature B has been approved (seperately or together)..............
This implicitly included (any) work needed for Common Bit (possibly twice)..........

If you weren't doing Feature B at all - you'd still need to do Common Bit (logicall there would be no seperate Common Bit to need approval) so whatever approval/authorisation you have MUST be OK.

The segregation/seperation of A from B is only a "technical" issue....
Obviously when you come to implementation (assuming they don't "go together") you have one less task for the Feature that goes 2nd (as Common Bit has already been done).

This is assuming that Common Bit is fairly trivial (Features A & B may or may not be - but it doesn't matter "much" as they have been justified already)

If Common Bit is in fact the major part of the change (with the features being trivial)
eg Common Bit is implementing a full Database schema and Feature A & B are trivial SQL reports
then:

a) You would appear to have saved a fair amount of resource - as the major work for Common Bit has been justified/costed and approved (twice).
b) You should possibly look at your Impact Analysis process..........

 

 

 

 

 

Johan Sundqvist's picture

Thanks Drew!

Your answer is a very good advice to seperate the changes into 3 parts, the problem for me is also how to handle this kind of scenario in a standard way.

Should I have a process for best practice in theses cases and train the development team to act according to some rules when these types of things occur.  (Most likely  the dev team that will spot this kind of problem).

Should we stop development and send both features back to the CCB with a recommendation that the also approve the new change “The common one”? 

Regards Johan.

 

 

Drew Benson's picture

It would seem to me that you have 3 "Changes"

1) The "Common" change (x)

2) The 2 other changes (a + b)

Both the "other" changes have a dependency on the "Common" change

 

(in theory) The Common change could be implemented independently
That might not be true - but logocally it isn't dependent on change a & b

Change "a" can only be implemented after/with change "x" 
"with" or without change "b".

Change "b" can only be implemented with/after change "x" 
"with" or without change "a". 

Depending on what (testing) environments you have/can use you may need to manage a couple of "instances" of Change "x" - but that shouldn't be to onerous.  

 

 

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.