Home/ Questions/Q 7078673
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T06:34:36+00:00

I am using ClearCase 7.1.2 and am working on a project. At some point

  • 0

I am using ClearCase 7.1.2 and am working on a project. At some point long before I came along there was a branch (lets call it ‘pilot’) which eventually became the production code while the main tree was left behind. At this point I need to make a branch off of pilot to implement a new feature but am running into a problem.

I have made my branch and all seems to go well when committing changes to existing files but when I do a mkelem the new file ends up on main. I want it on pilot. What would the config spec look like for this or what combination of commands can I piece together to make this a reality?

Right now my config spec looks something like this (going from memory):

elements * CHECKEDOUT
elements * main/0 -mkbranch pilot
elements * main/pilot
elements * main/LATEST

I’ll update once I can see what I have going on there.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You will find examples on the config_spec man page, as well as Config spec rules for elements in subbranches.

    What you need to do is first put a label on pilot branch (ie, on all the element present in your view on pilot branch), in order to make new versions from a fixed point in time.

    Then:

    elements * CHECKEDOUT
elements * .../my_feature_branch/LATEST
elements * LABEL_ON_PILOT -mkbranch my_feature_branch
elements * main/LATEST -mkbranch my_feature_branch

    Trying to make branch from the “LATEST” versions of another branch is really not recommended: you simply don’t know from what you are working on on your new branch.

    • 0