Import Base CC to RTC, how to handle so many labels?
Hi
I need to import this base CC vob to RTC and the project wants everything.
1. There seems only one "main" branch is in use. The 1A.systemtest doesn't have any file when I set the config spec to "element * .../1A.systemtest/LATEST" (pls let me if I am wrong).
2. The build process created tons of labels. How can I migrate these labels? Do I have to create an attribute on all of them? Is there a quick way to do this?
Thanks
Jirong
http://i55.tinypic.com/n4ts15.png
I need to import this base CC vob to RTC and the project wants everything.
1. There seems only one "main" branch is in use. The 1A.systemtest doesn't have any file when I set the config spec to "element * .../1A.systemtest/LATEST" (pls let me if I am wrong).
2. The build process created tons of labels. How can I migrate these labels? Do I have to create an attribute on all of them? Is there a quick way to do this?
Thanks
Jirong
3 answers
First of all, they can't get "everything" ... the can only get labeled
configurations. And if you want every configuration that was ever
labeled, yes, you'd need to put the import attribute on each of the
label types (not on the labels ... on the label types).
I'd suggest writing a script to do it, rather than doing it by hand.
Cheers,
Geoff
On 10/21/2011 3:23 PM, hujirong wrote:
configurations. And if you want every configuration that was ever
labeled, yes, you'd need to put the import attribute on each of the
label types (not on the labels ... on the label types).
I'd suggest writing a script to do it, rather than doing it by hand.
Cheers,
Geoff
On 10/21/2011 3:23 PM, hujirong wrote:
Hi
I need to import this base CC vob to RTC and the project wants
everything.
1. There seems only one "main" branch is in use. The
1A.systemtest doesn't have any file when I set the config spec to
"element * .../1A.systemtest/LATEST" (pls let me if I am
wrong).
2. The build process created tons of labels. How can I migrate these
labels? Do I have to create an attribute on all of them? Is there a
quick way to do this?
Thanks
Jirong
http://i55.tinypic.com/n4ts15.png
First of all, they can't get "everything" ... the can only get labeled
configurations. And if you want every configuration that was ever
labeled, yes, you'd need to put the import attribute on each of the
label types (not on the labels ... on the label types).
I'd suggest writing a script to do it, rather than doing it by hand.
Cheers,
Geoff
The "lstype" command includes three predefined label types, BACKSTOP, LATEST, and CHECKEDOUT.
What's the purpose of these predefined label types? Do I need to migrate these labels?
Thanks
Jirong
Those are "dummy" label type for use in version-extended naming. The CC
synchronizer will not allow you to synchronize those dummy label types.
Cheers,
Geoff
On 10/24/2011 2:08 PM, hujirong wrote:
synchronizer will not allow you to synchronize those dummy label types.
Cheers,
Geoff
On 10/24/2011 2:08 PM, hujirong wrote:
gmclemmwrote:
First of all, they can't get "everything" ... the can only
get labeled
configurations. And if you want every configuration that was ever
labeled, yes, you'd need to put the import attribute on each of the
label types (not on the labels ... on the label types).
I'd suggest writing a script to do it, rather than doing it by
hand.
Cheers,
Geoff
The "lstype" command includes three predefined label types,
BACKSTOP, LATEST, and CHECKEDOUT.
What's the purpose of these predefined label types? Do I need to
migrate these labels?
Thanks
Jirong