Cannot accept change from stream into workspace
Cannot accept changes into workspace from stream.
Steps: 1.created project area, created a stream, two workspaces(for two users), set up user roles. 2. set the targetflow between stream and workspaces, 3. loaded empty workspaces into sandboxes in my local machine by logging in different users, 4. checked in and delivered new files(45,000files) from one of the workspace into stream 5. accepted new changes from stream into another workspace cmd: lscm accept -c 5441 -r https:/xxx:9443/ccm -s RTCStream -t RTCWorkspace problem after waiting for 12 hours: Workspace unchanged. I can see the files are checked into stream from the browser admin console version: RTC5.0 server and client created new workspace by another userid: lscm create workspace -r https://xx:9443/ccm User3Workspace -s RTCStream lscm set flowtarget RTCStream User3Workspace -r https://xxx:9443/ccm lscm remove component User3Workspace RTCComponent -r https://xxx:9443/ccm(remove the component in new workspace since it contains all the files in stream) lscm add component User3Workspace RTCComponent -r https://xxx:9443/ccm(added component in new workspace) lscm load -d "c:\dataRTC\user3" -r https://xxx:9443/ccm User3Workspace lscm accept -c 5441 -r https://xxx:9443/ccm -s RTCStream -t User3Workspace >..\log.txt Problem: the changeset in stream was loaded in to the workspace in repository, but was not copied into sanbox "c:\dataRTC\user3" there is only on changeset 5541 in stream(another is the initial changeset)
showing 5 of 7
show 2 more comments
|
One answer
Are you loading your repository workspace to a local workspace or sandbox? If you haven't done this part, you wouldn't see any changes from that delivery.
You can do the load using the "lscm load" command.
Comments yes,I loaded the empty workspace into local workspace(sandbox) first, then checked in files, see the steps I made.
I don't want to use load because I want to get the changesets one by one from the beginning, don't want to get all of them at the same time.
I think it's too late if you've accepted all of the changes from the stream. The local workspace will always refer to the change sets that are in the repository workspace.
Your best bet is to create a new repository workspace, accept the first changeset, and then load the local workspace. Repeat this process with the following changesets until you get to the changeset that you want.
thank Robert for your quick response, I think it is not late, I am trying to accept the first changeset, but get nothing, my workspace in repository is empty, I did not accept all of changes from stream.
after I successfully loaded all the changes(there is only one new changeset) from Stream into workspace and sanbox, and then successfully discarded the changeset,
correct.. accept and load do different things. you can have a workspace or stream and NO sandbox, and still do Accepts of changes from other sources.
showing 5 of 6
show 1 more comments
|
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.
Comments
Can we see if there's any indication that the second workspace sees the stream? What is the result of an "lscm status" command?
You're dealing with a large number of files in that change set. You should contact support about your particular configuration and that it is an issue when you're accepting a large change set.
when I check the status, it is empty. but when I check the changeset list, it returns the changset number
I am just testing and learning RTC, there is no support, what configuration do I need to change?
I mean that your configuration of hardware and database might not be able to handle such a large change set. Given that you are testing RTC, does that mean you are using Derby or did you connect it to a production quality database?
When you move to production, I suggest that you avoid creating such a large change set. Try to split up any share operations into smaller change sets or even into multiple components. Check with the RTC sizing guide for more details.
sorry, I made a mistake, the file number is 45,000, not 450,000. I am using Derby , there is no production, only for test.
I can load the files into local workspace(sandbox), but not able to accept to local workspace(sandbox), when I do "accept", it pulls files into workspace in the repository, but not copies to local sandbox.
when I test RTC4.0.6, it worked well, but RTC5.0 is different.
45,000 is still a large number to check-in for one change set. Given that you're also using Derby for your testing (Derby is not production scale), it's no surprise that it is slow.
thanks, but the problem is not "slow", the problem is it cannot get file into sandbox.