Git
This screen allows creating a new bot through integration with a Git repository. The agent during execution will clone the repository and execute the script according to configuration. Below are the available fields and features:
Git Repository Requirements
To execute the bot correctly, the Git repository must contain the following files at the repository root, depending on the chosen language:
Language | Files |
---|---|
Python | main.py and requirements.txt |
JavaScript (Node) | main.js and package.json |
Binary (EXE/ELF) | main.exe or main.elf |
Shell (Bash) | main.sh |
Batch | main.bat |
PowerShell | main.ps1 |
Warning
If the files are not at the repository root as indicated, the bot will not execute correctly.
Fields
Name
- Description: Enter the bot name
- Expected Format: bot-xxx (example: bot-123)
Version
- Description: Specific version of the bot to be used.
- Expected value:
X.Y.Z
(example:1.0.0
)
Language
- Current value: Select a language from the list
- Description: Programming language used in the bot.
- Possible values:
Python
,JavaScript (Node)
,Binary (EXE/ELF)
,Shell (Bash)
,Batch
,PowerShell
Agent
- Current value: Select an agent from the list
- Description: Defines the agent responsible for bot execution.
- Important: Only 1 agent can be selected during bot creation.
Mode
- Current value: Select a mode from the list
- Description: Indicates the automation execution format.
- Possible values:
Headless
,Headless Parallel
,Headed 1920x1080
Repository URL
- Description: Complete address of the Git repository. Can be a public or private repository.
- Important: Make sure the repository is accessible.
- Example: https://github.com/my_username/my-repo.git
Parameters (Json)
- Description: Field to insert custom parameters in JSON format.
- Note: These parameters will be sent as environment variables during bot execution.
{
"arg1": "1366",
"arg2": "768"
}
Description
- Description: Free text to describe the bot’s function and purpose.
Authentication
The system offers two authentication options for repository access:
- No authentication: For public repositories.
- Authentication using token: For private repositories. The token must have read permissions.
Warning
The authentication token will need to be configured in the Sinfonia environment variables section.
Last updated on