Job Engine
Opsera's Job Engine reduces manual setup by establishing a unified model that simplifies interactions between components and services.
No-Code Creation Drag-and-drop CI/CD pipeline builder — no custom scripts needed.
Full Automation Automates repo detection, testing, deployment, and provisioning.
Toolchain Flexibility Integrates with any CI/CD, security, or cloud tool — no vendor lock-in.
Security by Design Automated vulnerability scans and compliance checks built in.
Unified Reporting Visual dashboards for pipeline health, resource utilization, and KPIs.
Self-Service Developers manage infra, configure environments, and deploy independently.
Supported Configurations
Run scripts in a defined order. Four types supported:
✍️Manual Entry: Scripts entered directly into the pipeline tool.
📁Repository Hosted: Scripts stored in a Git repo and referenced by path.
📚Script Library: Commonly used scripts stored in a shared library.
🌐URL Hosted:Scripts hosted at external URLs, referenced inline.
ℹ️ Environment variablespullRequestLink,pullRequestSourceBranch,
Define variables manually or via global parameters.
Manual Entry: Enter variable name and value directly. Full control over values during execution.
Global Parameters: Define at tool registry or pipeline level. Reusable across multiple pipelines.
Secrets are securely stored and injected during execution — never exposed in plain text.
💡 Define secrets as global parameters to reference them throughout the pipeline without exposing values.
Automate plugin deployment. Choose a plugin type and select repository tools.
🐙Git RepositoryConnect to Git-hosted plugin repos.
🐳DockerDocker-based plugin deployments.
📦Package NamesSpecify named packages to install.
🗄Registry ToolPull from a configured registry tool.
Define runtime environments using container size and image.
Container Size Ensure the environment has sufficient resources to run effectively.
Environment Image A snapshot including app code, dependencies, and runtime configs — ensuring consistency across pipeline stages.
Create Pipeline for Job Engine Workflow
Step 1: Create Pipeline Level Parameters
Parameters can be global (from tool registry) or pipeline-specific. Once created, they can be used in Run Jobs and Run Script steps.
🔄 Dynamic Job Control: Modify how jobs run based on input values or runtime conditions.
🔐 Secure Credentials: Handle sensitive data without hardcoding into scripts.
🔀 Multi-Workflow Support: Manage different workflows with varying requirements.
Open the pipeline → click the Parameters tab → click
+ New Parameter.Enter a unique Name.
Enable Encrypted toggle if storing a sensitive value. Cannot be changed once set.
Enter the Value and configure Access Control.
Click Create.
Step 2: Create Pipeline Workflow
Login → navigate to Pipelines → click
+ Create Pipeline.Click the Blank Pipeline option.
Add a new step in the pipeline creation.
Click the pencil icon → give the step a name → choose tool as
Run Job→ click Save.Under Step Settings, configure the job engine using the supported tabs: Scripts, Variables, Secrets, Plugins, Environment.
Step 3: View Pipeline Logs
After execution, navigate to Pipeline Logs in the Summary tab.
Click the Console Output row to view console log details.
📁 Logs ≤ 750KB
Automatically stored in Pipeline Activity Logs for immediate access and review.
📥 Logs > 750KB
Remain in the artifact service. Download via the Download Activity Log button.
Last updated