Error in lscm deliver command saying "Nothing to deliver. No outgoing changes were found."
Hi,
I am migrating streams from accurev to rtc, for one stream i am getting below error
Nothing to deliver. No outgoing changes were found.
I am migrating using shell script which first merge code in trunk (Say Base_Trunk) then creates one snapshot from it then maintenance stream.
First two streams (release1, release2) migrated successfully but for third stream (release3) i am getting this error (i am using component name say "my_component").
but lscm status command shows many unresolved changes like below
>>>> RTC workspace status is:
Workspace: (1253) "release3_workspace" <-> (1220) "Base_Trunk>
Component: (1229) "my_component"
Baseline: (1250) 5 "release2_SS"
Unresolved:
-c- /build.xml
-c- /build_config/product-version.properties
-c- /Script/dashboard_input/cubeMeta.xml
-c- /src/main/java/com/BusinessLogic/Bean/TestConfigureServi>
-c- /src/main/java/com/BusinessLogic/Bean/TestDataService/>
And it fails saying
>>>> Delivering to RTC...
Nothing to deliver. No outgoing changes were found.
Can anyone help me on this?
2 answers
Thanks Ralph, after further analysis i found that checkin is failing because of file encoding error
>>>> Start of check-in log:
Commit failed. Invalid encoding during checkin for:
/src/main/java/com/Framework/Event/Application/CounterUpdateListener.java (UTF-8)
/src/main/java/com/BusinessLogic/Helper/formulahelpers/FormulaHelper.java (UTF-8)
Problem running 'checkin':
Unable to checkin due to invalid file encoding or line delimiter.
>>>> End of Check-in log:
That's why nothing is going from undelivered to outgoing bucket hence lscm deliver is returning with error.
Is there any way to skip this encoding check?
Comments
1 vote