ToscaExecutionClient.sh (Linux) "--importResults" flag not considered

[pitschr]

I have impression that --importResults true has no effect for ToscaExecutionClient.sh because I do not see the results in the Tosca Project. but I can see the results on Tricentis DEX > Event Monitor.

As per documentation I expect that the results is imported in the Tosca Project, where we can then see the results in the Execution List on Tosca Commander (local installation, after "Update all" of course)

importResults | Import results into your Tosca project. Possible values are "true" and "false".

Can you please validate if the documentation is correct or if my understanding was wrong? Or perhaps there is a combination that prevents from importing the results into Tosca project? Thank you.

This is how I execute on our GitLab CI/CD:

      ./tosca_execution_client.sh \
        --toscaServerUrl "$TOSCA_DEX_HOST" \
        --events "$TOSCA_TESTEVENTS" \
        --projectName "$TOSCA_WORKSPACE_NAME" \
        --clientId "$TOSCA_CLIENT_ID" \
        --clientSecret "$TOSCA_CLIENT_SECRET" \
        --caCertificate "$TOSCA_CA_CERTIFICATE" \
        --creator "GitLab Pipeline #$CI_PIPELINE_ID (Branch: ${TOSCA_BRANCH_NAME})" \
        --importResults true \    <=================================== this line seem have no effect
        --pollingInterval 10 \
        --resultsFolderPath "$ARTIFACT_REPORTS_TOSCA"

[pitschr]

As per analysis with Tricentis support, one database file of Automated Object Service was corrupted.

On Tosca DEX Server:

1. Delete cache folder C:\ProgramData\Tricentis\ToscaServer\ToscaAutomationObjectService
2. Restart windows service in Task Manager ToscaAutomationObjectService (this will re-create the new cache folder above)

importResults now works as expected.

[billmallard]

A follow up to this - with the info from this I was poking around the file service. I realized the default settings for the auto-removal (run frequency, max logs, max processing time) could never work for us. Our logs were too large and the default timeout of 2 minutes I think meant the logs could never import the results.

I've changed it to run every 30 minutes with a maximum of 100 logs (still experimenting) and keeping the 2 minutes max time. and now we have results.

Thanks for the nugget that helps us get it working.