This integration empowers developers to use GitHub as their version control system. Users will automate the transfer of any workload object — such as tasks, calendars, scripts, and triggers — to and from GitHub. Often, this integration is used to support the development process, inclusive of propagating changes to the next environment, such as QA and Development. Support the automation of the DevOps process by integrating the Stonebranch Universal Automation Center (UAC) with GitHub.  Key Features: Import any Universal Controller (UC) object from GitHub into UC. For example: import a new template from the GitHub Marketplace into UC. Import any UC object from a script file into UC. For example: support for no internet connection from UC to GitHub. Export any UC object to GitHub from UC. For example: export a developed Universal Template to a GitHub repository. Export any UC object to a script object. The content of the script later can be used to import it on a Controller without needing the UAC import functionality. Support UC customers, whether SaaS or on-premises. Additional Information: Objects integrated with GitHub include Linux/Unix, Windows, and web service tasks. File operations are performed using the PyGithub module. This task supports Universal Agents for both Linux and Windows operating systems. Users can select different log-levels, e.g., info or debug. All passwords are encrypted using UC credentials. What's new in V 1.1.25With this release minor bugs are fixed.

The Stonebranch Jobs-as-Code (JaC) Universal Extension automates task and workflow delivery pipelines in which the job configuration is managed as code. This approach allows developers to create and manage job configurations using DevOps methodologies — complete with version control, testing, and continuous integration. The extension is configurable, allowing end-users to create jobs-as-code using the integrated development environment (IDE) of choice.The extension integrates with an external version control system (Gitlab, Github, or Bit Bucket), which stores the corresponding job definitions.Integrating with existing delivery pipelines, jobs can be stored on the external git repository and/or imported.Universal Automation Center (UAC) job definitions may be created through the Universal Controller (UC) user interface or as code in a development environment. Key Features:Query UAC definitions based on a variety of selection criteria. This feature can be used as a dry-run before exporting or importing to/from a Git repository.Export selected UAC Definitions to a Git Repository. After the export, this repository can be used as a backup or as a basis for developer collaboration on top of a source version control system.Import back to Universal Controller, UAC Definitions stored already in a Git repository. For UC version 7.3, or higher, the import feature can be triggered by using webhooks. GitLab/GitHub/BitBucket providers are supported.Total count of the selected/exported/imported UAC definitions.Detailed table representation of the exported/imported UAC definitions. What's New v 2.2.0EnhancementsThe Import Mode field, which offers two options, "Generic Webhook and Custom Mode" covering the existing Import functionality with Add/Modify/Remove lists and Webhook Payloads and "Insert or Update Mode" introducing new Import functionality with using single Modify list for creating/modifying and option for regular expressions.The Environment Variable UE_VERBOSE_LOG_FILE used for storing the logging information to a file provided by the user.Alphabetical sorting on the output of the Dynamic Choice Fields.Enhancements in the exceptions handling in case of invalid Git repository for GitHub. FixesFix Remove functionality when importing, and Git path displayed on STDOUT, if the name of the definition changes in the file on the Git provider. Fetching all branch files when Git Repository Path is set for GitHub.Implement a proper resource sorting algorithm by using a modified version of topological sort.Fix issues where string fields that looked like booleans were converted to actual booleans during yaml to json conversion.