It's all about the answers!

Ask a question

cannot see incoming changesets


samuel wang (321923) | asked Apr 23 '14, 5:35 p.m.

I created workspace,  set the flowtargets corretcly,

load workspace into my local: successfully,

C:\dataRTC>lscm load -d "c:\dataRTC\data" --all RTCWorkspace -r...
Successfully loaded items into the sandbox.

but in my local, when I check the status, I cannot see incoming changesets, it return nothing, but there are files in stream.

lscm  show  status -u admin -P admin -d "/"


Comments
2
sam detweiler commented Apr 23 '14, 5:45 p.m.

but just AFTER the load, you are at the same level as the stream you loaded from, so there would be no incoming change sets.

someone (else) has to deliver a change to the stream first.

9 answers



permanent link
samuel wang (321923) | answered Apr 24 '14, 9:53 a.m.
another member already delivered some changesets into stream before I loaded my workspace into local, my workspace in repository is empty, I cannot see any incoming changeset when checking status.

permanent link
sam detweiler (12.5k6195201) | answered Apr 24 '14, 10:07 a.m.
edited Apr 24 '14, 10:13 a.m.
>another member already delivered some changesets into stream before I loaded my workspace into local

you said 'before' you loaded, so those changes would have been included in you 'load' operation.

have them deliver something now,  after you loaded.

how can your workspace be empty? I thought Load always used a workspace.

I really dislike the commandline. too many parameters  with too many dependencies.

can u load up eclipse and look over the same sandbox folder/workspace/stream, and view the expected data,

then use the commandline to confirm it.

permanent link
samuel wang (321923) | answered Apr 24 '14, 10:16 a.m.

after another member already delivered some changesets into stream, I created my workspace, set the flowtargets, loaded my workspace into local(c:\dataRTC\data), this is the command I used:
C:\dataRTC>lscm load -d "c:\dataRTC\data" --all RTCWorkspace -r...
Successfully loaded items into the sandbox.

after loading, it is empty both in my local and my workspace in repository.

I expected to see the incoming changesets by checking the status, but cannot see, this is the command I used to check status:

lscm  show  status -u admin -P admin -d "/"

my purpuse is to get the changeset into my local one by one, not get all of them once.

 


Comments
sam detweiler commented Apr 24 '14, 10:46 a.m.

ok, I recreated what you did here on my dev system.  the workspace is empty.

you have to do an Accept first.

I don't see an lscm show command
I see changes in the stream
lscm list changesets -r https://server:port/ccm -u user -P password -w stream_name

Change sets:
  (1003) ---$ sam "fixup dates" 22-Apr-2014 09:37 AM
  (1004) ---$ sam "fixup comments" 22-Apr-2014 09:37 AM
..
..
i do NOT see changes in the workspace (yet, no 'accept' done)

lscm list changesets -r https://server:port/ccm -u user -P password -w workspace_name

No change sets found.


permanent link
samuel wang (321923) | answered Apr 24 '14, 12:45 p.m.

thaks, but I am not able to accept a change set, I stop all daemons, deleted my local workspace, re-loaded again, restarted my PC, but still get same error, see the result:

C:\dataRTC\data>lscm accept -s 1033 -t RTCWorkspace -r url:9443/ccm -c 1040
Problem running 'accept':
Update failed
Unable to obtain all component locks.
An error has occurred. Kindly check the log for more details.

C:\dataRTC\data>lscm accept -s 1033 -t RTCWorkspace -r url:9443/ccm -c 1039
Problem running 'accept':
Update failed
Unable to obtain all component locks.
An error has occurred. Kindly check the log for more details. 


permanent link
sam detweiler (12.5k6195201) | answered Apr 24 '14, 1:44 p.m.
well, its not -s 1033

its -s stream -c 1033

but I get a 'component not in workspace' error.. even with --flow-components

Comments
Michael Valenta commented Apr 24 '14, 3:02 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

What is the output of "lscm status"?


permanent link
samuel wang (321923) | answered Apr 24 '14, 2:29 p.m.

this command should be correct,
lscm accept -r url:9443/ccm -s 1033 -t RTCWorkspace -c 1039

1033 is the uuid of the source stream, 1039 is the uuid of changeset whcih I want to accept,

 Usage: lscm accept [-r/--repository-uri <arg>] [-s/--source <arg>] [-t/--target <arg>] [-b/--baseline |
                   -C/--components | -c/--changes] [selectors...]


permanent link
samuel wang (321923) | answered Apr 24 '14, 3:53 p.m.

there is no output for status, it is empty.

C:\dataRTC\data>lscm show status

C:\dataRTC\data>lscm status

C:\dataRTC\data>scm status
Problem running 'status':
Could not initialize data area. Could not lock C:\dataRTC\data - locked by other
 process.

C:\dataRTC\data>scm daemon stop --all
Daemon successfully terminated

C:\dataRTC\data>lscm login -r url -u admin
 -P admin
Logged in to url/ccm

C:\dataRTC\data>scm status


Comments
sam detweiler commented Apr 24 '14, 4:04 p.m. | edited Apr 24 '14, 4:05 p.m.

I also get no results for status.

my eclipse ui shows me incoming from the stream to my workspace. (prior to accept from the commandline)

 


Michael Valenta commented Apr 24 '14, 4:11 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

I wonder if this is related to the use of the -d option on load. Could you try the load without using that option?


permanent link
samuel wang (321923) | answered Apr 24 '14, 4:51 p.m.
edited Apr 24 '14, 4:52 p.m.
loaded workspace again, still cannot accept a change set, cannot see incoming change sets, see the result:
C:\dataRTC>lscm login -r url -u admin -P admin
Logged in to url

C:\dataRTC>lscm load -r url -i RTCWorkspace
Successfully loaded items into the sandbox.

C:\dataRTC>lscm status
Workspace: (1043) "RTCWorkspace" <-> (1033) "RTCProjectArea Stream"
  Component: (1044) "RTCWorkspace Default Component" (outgoing addition)
    Baseline: (1046) 1 "Initial Baseline"

C:\dataRTC>lscm list changesets
Change sets:
  (1045) ----$ samuel wang "Initial for RTCWorkspace Default Component" 23-Apr-2
014 04:57 PM
  (1042) ----$ samuel wang "Share" 23-Apr-2014 03:58 PM
  (1041) ----$ user1 "test delivery" 23-Apr-2014 03:02 PM
  (1036) ----$ user1 "test delivery" 23-Apr-2014 10:05 AM
  (1037) ----$ user1 "test delivery" 23-Apr-2014 10:05 AM
  (1038) ----$ user1 "test delivery" 23-Apr-2014 10:02 AM
  (1039) ----$ user1 "test delivery" 23-Apr-2014 10:02 AM
  (1040) ----$ samuel wang "Initial for RTCProjectArea Default Component" 22-Apr
-2014 04:19 PM

C:\dataRTC>lscm accept -r url -s 1033 -t RTCWorkspace -c 1039
Problem running 'accept':
Update failed
Unable to obtain all component locks.
An error has occurred. Kindly check the log for more details.


Comments
Michael Valenta commented Apr 25 '14, 8:09 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

From the status, it appears you are flowing to the "RTCProjectArea Stream". Is this the stream that has the change sets your co-worker delivered? Could you run the command "lscm list components 1033". That will show us what components are in the stream.

It also appears that you have the component "RTCWorkspace Default Component" in your workspace but that component does not exist in the stream. This could be why the accept is failing. It tries to lock the component in the stream but this fails because the component isn't there. Could you do a "lscm list components 1043" to see what components are in your workspace?

From the change set list, it appears that all the change sets are in the "Initial for RTCWorkspace Default Component" already. Perhaps you could try "lscm accept -r url -t 1043-c 1039" and see what the result is.


Tim Mok commented Apr 25 '14, 11:37 a.m.
JAZZ DEVELOPER

The result of the 'list changesets' command isn't a result of the workspace or the stream. Neither were specified so that list of change sets could be from any component, anywhere. I'm guessing that your workspace is using a different component than the stream based on the result. The two initial change sets listed have default comments and your status result with the outgoing component addition that suggest that you have two different components.


permanent link
samuel wang (321923) | answered Apr 25 '14, 11:01 a.m.
edited Apr 25 '14, 11:05 a.m.
Appreciate, you are right, the components are different in the stream and in my workspace, the names are same, but UUIDs  are different.
when creating new workspace without using "-s" ,  it give a new component in my workspace which name is the same as the component name in stream, but UUID is different,
if I create workspace with the parameter "-s", it adds the component of the stream in my workspace, and load all contents into my workspace,
so I recreated my workspace without using parameter "-s", after that deleted the default component in my workspace, added the component of the stream in my WS,  accepted a changeset, loaded it into local without using parameter "-d",  then check the status, I am able to see the incoming chnagesets.
but there is another question, I am not able to list the component of the stream(just wondering why), see the result:
C:\dataRTC>lscm accept -r url -s 1033 -t R TCWorkspace -c 1039
Repository:url
Workspace: (1049) "RTCWorkspace"
  Component: (1034) "RTCProjectArea Default Component"
    Change sets:
      (1039) ----$ user1 "test delivery" 23-Apr-2014 10:02 AM
        Changes:
          --a-- \text\

C:\dataRTC>lscm load -r url  RTCWorkspace
Successfully loaded items into the sandbox.

C:\dataRTC>lscm status
Workspace: (1049) "RTCWorkspace" <-> (1033) "RTCProjectArea Stream"
  Component: (1034) "RTCProjectArea Default Component"
    Baseline: (1035) 1 "Initial Baseline"
    Incoming:
      Change sets:
        (1041) ----$ user1 "test delivery" 23-Apr-2014 03:02 PM
        (1036) ----$ user1 "test delivery" 23-Apr-2014 10:05 AM
        (1037) ----$ user1 "test delivery" 23-Apr-2014 10:05 AM
        (1038) ----$ user1 "test delivery" 23-Apr-2014 10:02 AM

C:\dataRTC>lscm list components 1033
Problem running 'list components':
Workspace not found


Comments
Michael Valenta commented Apr 25 '14, 11:23 a.m.
FORUM MODERATOR / JAZZ DEVELOPER

I'm not sure why that doesn't work but I'm not a CLI expert. Perhaps it only works for workspaces that are loaded.

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.