For Olympus we already utilize cloudbees. The problem is that there are a lot of manual steps since the webrtcomm code needs to be manually pushed to the Olympus repo. Consider automating the whole process.
Also investigate end-to-end testing and see how we can take advantage of https://github.com/RestComm/webrtc-test for some basic tests that can be done from the CI job to get an indication of basic scenarios work. We could trigger scenarios of calling cloud.restcomm.com (although I'm a bit sceptical what would happen if something went wrong and too much load was imposed on the production server; we need to plan this carefully)
For Olympus we already utilize cloudbees. The problem is that there are a lot of manual steps since the webrtcomm code needs to be manually pushed to the Olympus repo. Consider automating the whole process.
Also investigate end-to-end testing and see how we can take advantage of https://github.com/RestComm/webrtc-test for some basic tests that can be done from the CI job to get an indication of basic scenarios work. We could trigger scenarios of calling cloud.restcomm.com (although I'm a bit sceptical what would happen if something went wrong and too much load was imposed on the production server; we need to plan this carefully)