mrsombre

Hello, @dikkatdeli Currently plesk for docker not intended for production use, but only for demonstration purposes of UI and API. Try to set network settings for container as host https://docs.docker.com/network/network-tutorial-host/....

Hello, @Morsalin1342 Unfortunately, plesk for docker not intended for production use, but only for demonstration purposes of UI and API. Production use of docker can be achieved in future, but...

Currently plesk in docker is not intended to production usage. Please, use it as described in readme file.

i'm sorry, not a number, but an id. so, if v1 api is synchronous, we already know numeric id when api answers on creating launch / suite, but as i...

Try this two environment variables ``` LOGGING_LEVEL_COM_EPAM_TA_REPORTPORTAL_WS_CONTROLLER: info LOGGING_LEVEL_COM_EPAM_TA_REPORTPORTAL_WS_RABBIT: info ```

Same for our pipeline, we used retry=true before for every test report (as mentioned in docs https://reportportal.io/docs/developers-guides/RetriesReporting). But it was broken after update. So, we spent some time on investigation...

I.m using RP in docker. As regular maintenance procedure i updated `reportportal/service-api:5.11.1` to `reportportal/service-api:5.14.1`. I checked on local deployment in docker that i could login, start launch and send some...

Btw fixed setting RP_JWT_SIGNING_KEY env variable for uat to a long string > 50 chars