It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882

question asked: Feb 09 '17, 8:19 a.m.
question was seen: 1,423 times
last updated: Feb 10 '17, 2:30 p.m.

Related questions

Any risk if we migrate CVS code to Existing RTC PA

0
Prashantha Kumari (3●5●11) | asked Feb 09 '17, 8:19 a.m.

Hello,

            We are planning to migrate CVS code to RTC. Is there any risk if we migrate CVS code to Existing RTC  PA? Project area is having some team areas and many workitems which are in use. But there is no source code. Component/stream is empty.

Thanks,
Prashanthi.

Accepted answer

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Feb 09 '17, 5:07 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

If the question is whether it matters if you import into an existing project area vs. importing into a new project area, the answer is no, it doesn't matter.   As Ralph says, you don't really import source code into a project area ... you import source code into one or more components.

Ralph Schoon selected this answer as the correct answer
Comments
Prashantha Kumari commented Feb 10 '17, 1:51 a.m. | edited Feb 10 '17, 2:23 p.m.

Hello Ralph/Geoffrey,

        Yes i mean to say it is importing to component only. As we had many WI in that particular PA which is already in use. So just wanted to get clarification, if we migrate to component of an existing PA which is used for WI, will it be risky ( in case if any problem comes during migration, any issue with existing WI).

I tested this migration on test environment with newly created PA. But i didn't face any issue. But I need to take precaution, before i migrate to production server.

Thanks for your suggestions and reply.

Prashanthi.

Geoffrey Clemm commented Feb 10 '17, 2:30 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I can only repeat that you are not importing into a project area, you are importing into a component.   The only relevance that a project area has for a component is that a component references the project area that it wants to get its permissions and process pre/post conditions from.   So importing into a component has no effect on anything in the project area (such as work items).   Now if you are asking whether it matters whether you import into an existing component or a new component, then that is a valid question, and the answer is "yes" (but it doesn't look like that is what you are asking).

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Feb 09 '17, 8:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 Based on what information in your question do you assume one can do a risk assessment?


Some general import considerations
If you just import the code say into an Eclipse project and share the code into RTC, there is no risk I can see.

If you want to  use the CVS import with history, I would argue that you shouldn't. You should keep the CVS system for the old code and just import the last baseline. If you still want to do an import, test this on a test system first.

Note that code is not so tied to project areas and can can be used across project areas. The ownership of SCM items can also be changed from one project area to another. 


Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.