It's all about the answers!

Ask a question

What is the expected latency after delivery?


Andy Jewell (24236274) | asked Nov 19 '13, 7:57 p.m.
After I check a file in, there seems to be a minute or two of latency before that change is "seen" by other streams.  For example:

C:\Users\O386600\build-process-test\master>lscm accept -C master <-- first minute
Password (O386600 @ https://repo.org/ccm1/):
Workspace unchanged.
C:\Users\O386600\build-process-test\master>lscm accept -C master <-- minute "or so"
Password (O386600 @ https://repo.org/ccm1/):
Workspace unchanged.
C:\Users\O386600\build-process-test\master>lscm status <-- confirm it's there
Password (O386600 @ https://repo.org/ccm1/):
Workspace: (2032) "build process test o386600" <-> (2036) "Build Process TEST"
  Component: (2025) "master"
    Baseline: (2031) 5 "master-1.0"
    Incoming:
      Change sets:
        (2046) ---$  5818 "BATCH UAT3: NA_MBE_MP_UAT_SweepNewAddress & NA_MBE_M>
C:\Users\O386600\build-process-test\master>lscm accept -C master <-- now it sees it
Password (O386600 @ https://repo.org/ccm1/):
Repository: https://repo.org/ccm1/
Workspace: (2032) "build process test o386600"
  Component: (2025) "master"
    Change sets:
      (2046) ---$  "Fix call to getFileComment from forcestep" 19-Nov-2013 04:38 PM
        Changes:
          ---c- \master\buildSrc\src\main\groovy\ArfMaker.groovy
          ---c- \master\gradle.properties
        Work items:
          (2034) 5818 "BATCH UAT3: NA_MBE_MP_UAT_SweepNewAddress & NA_MBE_MP_UAT..."

In this example, I had made a delivery TO the build-process-test stream and then just had to wait a bit to see it.  I suppose in usual circumstances this one or two minutes (have not timed it) wouldn't be too much of a problem but it would be good to have an understanding and expectation for this latency.

Any suggestions?


- Andy


Accepted answer


permanent link
Shashikant Padur (4.2k27) | answered Nov 20 '13, 1:58 a.m.
JAZZ DEVELOPER
edited Nov 20 '13, 2:00 a.m.
Andy,

The command line does not automatically refresh and so is not aware of an incoming change. You need to run 'lscm status' which connects to the server and looks for updates. Once the lscm/daemon is aware of an incoming change, you should be able to accept the changes immediately.
We do have automatic refresh in Eclipse/Visual Studio clients only in Windows platform but that preference is not enabled by default. The preference is not yet in the cli client.
Andy Jewell selected this answer as the correct answer

Comments
Andy Jewell commented Nov 20 '13, 10:47 a.m.

Ah, that's great.  I thought it was just a coincidence that every time I did a status it would find the updates.. :)  Thank you!


Geoffrey Clemm commented Nov 22 '13, 12:01 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

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.