Universal Automation is PowerShell specific. Unlike Jenkins, it does not require the installation of a separate plugin to execute PowerShell scripts. Universal Automation also integrates with features of PowerShell such as Read-Host and Write-Progress to provide a more native PowerShell experience. Just as with Jenkins, it does collect script output.
Both Jenkins and Universal Automation can execute scripts and schedule scripts to run.
Both Jenkins and Universal Automation allow for users to provide parameters to scripts when running them. Universal Automation doesn’t require any configuration for these parameters as they will be interpreted from the param block of your scripts.
Jenkins has the concept of projects, pipelines, and steps. Universal Automation’s architecture is simpler and doesn’t have the same level of organization. Scripts within UA can trigger other scripts to achieve pipeline-like functionality.
UA and Jenkins both other role-based access. UA provides authentication through its Universal Dashboard website. This requires some configuration of UA.
Jenkins requires the installation of Java as well as the Jenkins server itself. UA is distributed as a PowerShell module and can be downloaded using PowerShellGet.