PDA

View Full Version : [FIXED] Unable to configure archive server



danguba
18 Dec 2015, 7:37 AM
I have created storage.json as instructed in http://docs.sencha.com/sencha_test/command_line_archive_server.html and server started correctly

Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. All rights reserved.


d:\studio-cli>studio-cli.cmd server
Archive server listening on port 1903

But when I point Sencha Studio to http://localhost:1903 it gives me error

Failed to load remote archive catalog: http://localhost:1903/catalog.json

dongryphon
18 Dec 2015, 9:28 AM
Thanks for the report! I have opened a bug in our bug tracker.

dongryphon
18 Dec 2015, 9:28 AM
I suspect the issue is that without runs in the archive the catalog.json is not created. We'll look into it.

kkrohe
18 Dec 2015, 11:59 AM
The archive server doesn’t yet create the needed root catalog.json files during startup. Those get created when archives are uploaded during CLI test runs, but you can also manually create the needed catalog.json files as well.

To have the runner automatically update the archive server with the new test run results, you’ll need to add some extra parameters to the run command.

Following the example commands available at http://docs.sencha.com/sencha_test/command_line_archive_server.html, a command to run tests and upload to the archive server would need these options:


studio-cli run -o output -p pool -s [scenario] -S archiveServerUrl -K archiveServerKey -n buildNumber


Based on the sample server.json config in that guide, if your server.json config contains:

{
"889jwx093jr8wuwer": {
"path": "/developers"
},
"sccmnn840394843": {
"path": "/qa"
}
}


then a run command to automatically upload the results of a build (100, for example) to the /qa directory of an archive server running locally with that config would look like:

studio-cli run -o output -p pool -s [scenario] -S http://localhost:1903 -K sccmnn840394843 -n 100


The file locations themselves are relative to the storage.json file. The server uses a folder named “storage” located next to the storage.json file to contain the storage areas, and each configured storage area needs to contain a catalog.json file.

For the above example, this would be a file located at ‘storage/qa/catalog.json’ next to the storage.json file with the following content:

{
“archives”: {}
}