scm accept command will not accept changes for remote workspace.
Serge Blokhin (26●7●11)
| asked Nov 22 '13, 3:54 p.m.
retagged Dec 16 '13, 1:10 p.m. by David Lafreniere (4.8k●7)
hi
if i'd like to accept changes for a not loaded locally workspace scm does not seem to work. however i can do it from eclipse client. is that a bug or i am doing something wrong?
|
2 answers
Shashikant Padur (4.3k●2●7)
| answered Nov 24 '13, 11:34 p.m.
JAZZ DEVELOPER edited Nov 24 '13, 11:35 p.m.
The scm cli remote accept should work. Could you paste the command and also the output including any error encountered?
Also mention the RTC version of the client.
Comments hi,
well, it doesn't give any errors. it just says "workspace unchanged"
the command i am using is this:
lscm.bat --show-uuid y accept -t <workspace> -r <repository url> -C <Component name>
this workspace is not loaded on the machine i am executing the command on. What's interesting is that i can accept incoming changes from the other machine using eclipse client or cli. but it's not working on the machine where i am actually trying to accept changes. by the time i am trying accept the changes the workspace is not loaded anywhere.
see below version command output.
Have you got any other workspace loaded in that machine? Run 'scm ls daemon' and the output lists the daemon and the sandbox it is registered with. Try stopping all daemons: 'scm daemon stop -p {port}'. Rerun 'lscm accept' and see if it works.
yes i do have 1 workspace loaded on that machine.
good point. i did run scm list daemons and it listed over 20 of them. I was wondering why cli runs so many of them? i stopped all of them but it didnt solve the problem. if i make a change and try to accept for the remote workspace it keeps saying "workspace unchanged" and the history command does not list my changes... some updates:
looks like scm.exe command is a lot more consistent with accepting changes for a remote/unloaded workspace. i see it works for me. lscm.bat works only if i stop all the daemons. i think it's a bug.
lscm launches one daemon per sandbox. Did the 20 daemons had a sandboxes registered under it? 'lscm list daemons' would show that.
In lscm (daemon) mode, since there is state maintained for workspaces/streams it does not refresh remote changes before executing the accept command. Yes this a defect. We should force a refresh or at least provide an option to force a refresh. The following workitem will address this issue: https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=291053
well, i do see only one daemon listing the sandbox but the rest of the daemons dont list any sandboxes... so something is not the way you describe. Usually you should see only one daemon per sandbox and probably one additional daemon if you have run a remote operation from a non-sandbox location. oh ok, that makes more sense since i do accept operation for a lot of different remote workspaces.
showing 5 of 8
show 3 more comments
|
|
the rtc client cli version:
com.ibm.team.filesystem.cli.client, version 3.1.300.v20130426_0115
Provides Subcommands:
load, login, logout, create, create/workspace, create/baseline,
create/changeset, create/snapshot, create/component, create/loadrules,
create/stream, changeset, changeset/comment, changeset/complete,
changeset/current, changeset/relocate, changeset/associate,
changeset/disassociate, changeset/suspend, changeset/resume,
changeset/discard, changeset/extract, changeset/locate, change-target,
change-target/workspace, change-target/component,
change-target/unset-workspace, list, list/workspaces, list/projectareas,
list/teamareas, list/streams, list/components, list/remotefiles,
list/credentials, list/daemons, list/snapshots, list/locks, list/properties,
list/changes, list/users, list/baselines, list/changesets, list/states,
list/flowtargets, list/preferences, checkin, accept, deliver, status,
validate, conflicts, resolve, move, lastmod, share, discard, undo, compare,
history, diff, repair, workspace, workspace/change-target,
workspace/component, workspace/unset, workspace/add-components,
workspace/remove-components, workspace/replace-components, workspace/delete,
workspace/unload, workspace/propertylist, workspace/propertyget,
workspace/propertyset, workspace/add-flowtargets,
workspace/remove-flowtargets, workspace/flowtarget, component,
component/propertylist, component/propertyget, component/propertyset,
baseline, baseline/propertylist, baseline/propertyget, baseline/propertyset,
property, property/list, property/get, property/set, property/remove, lock,
lock/list, lock/acquire, lock/release, annotate, snapshot, snapshot/promote,
snapshot/propertylist, snapshot/propertyget, snapshot/propertyset, refresh,
users, users/set, delete, delete/state-content, changeaccess, extract,
extract/file, debug, debug/fetch, debug/fetch/changeset,
debug/fetch/component, debug/fetch/workspace, debug/fetch/item,
debug/fetch/uri, preference, preference/get, preference/set
com.ibm.team.filesystem.cli.tools, version 3.1.300.v20130503_0103
Provides Subcommands:
tools.verify, tools.validate, tools.echo.stdin, tools.configvalue, tools.log,
tools.generatehelp, tools.dump, tools.dump/postprocess
com.ibm.team.rtc.cli.infrastructure, version 3.1.300.v20130425_0448
Provides Subcommands:
help, version
|
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.