Runner
Last updated
Last updated
You can always find the current download link .
The installation process on the occasion of a fresh system is several steps which are listed below, in the case of steps that were previously performed on a particular computer, you can skip individual steps.
The first step would be to install a package manager if you still don't have one, for Windows this would be choco, and for macOS homebrew.
To do this you need to paste the following command into Powershell or Terminal respectively.
If you have encountered any problems, it is recommended to check the program's documentation, which for Windows can be found and for macOS .
If you use Windows you will also need to install git, which you can do by running.
The next step will be to install Chrome and Chromedriver.
In the next step, we will install python.
If you encounter a problem with pip installation, you can use instead of command above:
In this step, we will take care of the installation of Ruby.
The final step will be to install imagemagic.
In addition, on Windows, you need to download msys2 and you can do this with the following command.
On macOS, when you launch the application, the first screen you see will inform you of the current status of your granted permissions.
You need to click the buttons one by one which will open the appropriate tab in the settings and grant all the necessary access to the application.
After doing this, the window will close and you can proceed to the next step.
to be released...
The meaning of the different statuses of the tray icon:
//A - no connection to the server or a bad authorization code or the last task performed has failed (for 5 min after the task).
//A - there is a connection to the server, everything ok.
//A - task in progress.
//A - the last task done correctly (shown for 5 min after the task).
At this stage, you should turn on the applications and fill in the "Portal URL" and "Bot secret" fields. Portal URL - is the address of your portal. Bot secret - is a field for the bot secret that you created earlier in the portal.
After filling in the above fields, your application should look like this.
After doing so, click Save and the application should disappear after that you can proceed to the next step to run your first job.
In Activity Monitor we can see the current status of the bot, copy the id of the job that was or is currently being executed, and open the folder for that job.
The main part of the screen is where the output of the job will appear.
At the very bottom, there is a text field that can be used to provide the bot with the data it needs from the user if the job requires it, and a send button that will send what you type in the text field. An alternative way to send is to press enter, which can be turned on or off by clicking the checkbox next to it. The last button is the Kill button which, when used during the execution of a job, will abort it.
In the preferences, you will find the configuration options for the bot and the info tab which will allow us to check the current status of the necessary dependencies.
Portal URL - address of your portal.
Bot secret - the secret code of the bot from the portal you want to associate with this runner.
Start with system - whether the runner should turn on with the system start.
Keep running no matter what - whether the application should automatically relaunch when closed.
Enable visual automation on port - starts the visual automation server on the indicated local port at runner startup.
Clean jobs folder after -after how many days should the jobs folder be cleaned up.
A simple screen that will show us if we have all the necessary things, where green color means that everything is ok and red color means that a particular thing is still missing.
Appears when you press CTRL-D while in the Preferences menu, and an additional Debug menu shows up.
Update channel - select update channel.
Crash test - crashes the app, the exception should then be sent to sentry.
Debug in activity - shows request from / to server and answer in console.
Save - saves the settings.
If you are using Windows before proceeding further you must first download .NET Runtime 5.X from .
Kill process matching - enables the options to remove processes on the runner's machine that meet the typed regex using one of 3 ways (Close, Kill or Kill with children) after every job executed (after every) or after a job that failed to execute properly (after failed). The regular expression is typed according to the standard used for the .
