Is there a way to accept incoming changes identified by a work item query (work items located in other & friend jazz instance) ?
Hi,
We have to accept changesets from work items that are considered approved (can be identified by a RTC query) into a dedicated build workspace.
Our work items and source code changesets are located in different instances of RTC (but same version 4.0.3). (So change sets are considered as "Remote Change Sets" in work items)
Is there any way to perform this action ?
Thanks
Gael
We have to accept changesets from work items that are considered approved (can be identified by a RTC query) into a dedicated build workspace.
Our work items and source code changesets are located in different instances of RTC (but same version 4.0.3). (So change sets are considered as "Remote Change Sets" in work items)
Is there any way to perform this action ?
Thanks
Gael
5 answers
Hi Abraham,
What do you mean by Distributed SCM (is this scm command line ? ) ?
Do you have any link to examples/documentation about this tool ?
Thanks a lot in advance
Gael
What do you mean by Distributed SCM (is this scm command line ? ) ?
Do you have any link to examples/documentation about this tool ?
Thanks a lot in advance
Gael
Hi Gael,
let me know if the following helps
Flowing Changes to different repositories
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=%2Fcom.ibm.team.scm.doc%2Ftopics%2Ftflowchangestodiffrepo.html
enabling Distributed SCM
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=%2Fcom.ibm.team.concert.dotnet.doc%2Ftopics%2Ftenabledistribscm.html
let me know if the following helps
Flowing Changes to different repositories
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=%2Fcom.ibm.team.scm.doc%2Ftopics%2Ftflowchangestodiffrepo.html
enabling Distributed SCM
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0/index.jsp?topic=%2Fcom.ibm.team.concert.dotnet.doc%2Ftopics%2Ftenabledistribscm.html
Comments
Hi Abraham,
The "Flowing Changes to different repositories" solution would help us if our stream was a little bit smaller. For information, our stream is containing more than 8GBs of source code with a enormous history so we can't plan such action.
Thanks for this solution but it seems we need another one.
Gael