Hi ... we are using 19.1 robotic runtime and 8.5.1 robot manager/sync server/package server . We would like to enable the dev-op process to build/deploy/test the robotics solution in the automated fashion.
The ideal flow is that developer checkin the code, and the package is compiled and deployed automatically to the server, then the bot is started automatically with the new package to start the test.
Step 1: developer develop the automation in robotic studio or visual studio plugin.
Step 2: developer checkin the automation code in Git repo.
Step 3: Build machine (Jinkens) get the latest automation code and auto compile into the automation package with build #
Step 4: From Build machine, the package is added automatically into package server to replace the old version.
Step 5: From Build machine, automatically trigger the start of the automation ( through robot manager?) to run the testing.
I am not sure if it is possible. Hope you can share some lights.
***Edited by Moderator: Pooja Gadige to add platform capability tag***
@walterw1677 This isn't functionality that is officially supported. I have seen posts here where some users have stated that they can get the build to work by analyzing the StudioLog and gathering the relevant commands from there, but there's nothing official from Pega with regards to how you would do this or documentation around it. This wouldn't take care of the deployment steps though, which would be to publish the version you've deployed to Robot Manager and Package server and then to deploy that version in Robot Manager. Those are most likely REST service calls though that you might be able to replicate. I would suggest speaking to your Client Success Manager to get this as a feature you are interested in.