Cannot find file when deploying via avm deployment receiver on Test server
1. Create 2 machines (system1 and system2)
System 1 will be the receiver and system 2 will be the source
2. On System 1 create a Web Project called testA-live
3. On System 2, create a new web project called testA.
4. In the "Configure Recievers" section, add system 1 as a Deployment Receiver.
e.g. Type: Test Server, Display Name: System1, Transport Name: default, Host: host_system1
Port: 50500, username: admin, password: admin, Target Name: avm
5. in the admin sandbox, add a file (a.txt) and submit it
6. Submit the changes to staging
7. Deploy the snapshot to System 1 - gui reports a successful deployment
8. Verify exist content on system2 in testA-live
testA-live web project should contain deployed file (a.txt) OR if web-project testA-test is created on 2 step then it should contain file (a.txt) OR allow to create web project with DNS name with "--" (e.g.testA--"user_name"-live)
testA-live doesn't contain file (a.txt)
Node: If Open the Node Browser you see "testA--"user_name"-live" store
Alfresco 3.2r 415 Windows 2008 SP1 x64, Tomcat 6.0.18, Mysql 5.1.39, JDK 6u16 x64
[This issue has been reassigned to email@example.com as part of the Alfresco cloud migration project. The reporter of this issue was alfrescoqa]
The component originally used was not a supported, recognisable system component with an associated component owner. Either the component never existed (it was fictional) or it has reached end-of-life.
The issues will be closed. Reopen and assign to an existing system component if necessary. Use labels appropriately.
[This comment has been reassigned to firstname.lastname@example.org as part of the Alfresco cloud migration project. The author of this comment was alfrescoqa] Closed as won't fix. DariaV
[This comment has been reassigned to email@example.com as part of the Alfresco cloud migration project. The author of this comment was rmanthena] Assigned to Alfresco QA Team for testing.
Please use head build 643 and SVN revision number 31912 or later to test this issue.
[This comment has been reassigned to firstname.lastname@example.org as part of the Alfresco cloud migration project. The author of this comment was mrogers] And its a test error 8-(
As per the comments of 14 May 10 - Deploying to avm://[Project Name]--admin-live store implies that it was admin's authoring sandbox that was deployed to the live server. I also note that this is in the description so was my oversight and I should have rejected sooner. Authoring sandboxes should only be deployed to test servers, likewise only staging sandboxes should be deployed to live servers. There's not a lot of difference but as you can see by this bug the store names are slightly different.
MER - Edited - I reread yet again and saw that it was an authoring sandbox deployed to a test server However Ben has already previously decided that the deploy to another authoring environment is not supported.
AVM deployment is working correctly, look in the node browser to compare store names rather than trying to deploy from one authoring environment to another.