GitHub Actions

Run your existing GitHub Actions workflows and get unified visibility, compliance monitoring, and AI-powered insights — without changing how you build.

Why use Opsera with GitHub Actions?

What you get	What it means
Unified dashboards	See all workflow runs across every repo in one place
Real-time logs	Stream live output from every step as it runs
AI summaries	Get instant analysis of failures, misconfigs, and violations
Compliance monitoring	Catch vulnerabilities before they reach production
Dynamic parameters	Override pipeline settings at runtime without editing YAML
No lock-in	Bring your own tools — Opsera plugs in, not over

Prerequisites

Before you configure a pipeline, make sure you have:

• A GitHub repo with at least one active Actions workflow (.github/workflows/*.yml)

• GitHub registered in Opsera Tool Registry → How to register a tool

• Webhook configured on the pipeline before clicking Register Webhook in the step

Heads up: If the GitHub Actions step is the first step in your pipeline, it can only be triggered via webhook — not manually from the UI.

Setup

1. Create a pipeline

Opsera → Pipelines → + New Pipeline

2. Add the GitHub Actions step

1. Click the Unconfigured step

2. Enter a step name

3. Select GitHub Actions Workflow as the tool

4. Add tags if needed → Save

3. Configure the step

Under Step Settings, fill in:

Field	What to select
GitHub Tool	Your registered GitHub integration
Repository	Target repo
Branch	Branch to watch/trigger on
GitHub Actions Workflow	The workflow name (from your .yml file)
Workflow Job	Specific job within that workflow

Then click Register Webhook to connect Opsera ↔ GitHub.

Triggering pipelines

1

Option 1 — Manual (Opsera UI)

Open the pipeline → click Start Pipeline. Not available if GitHub Actions is the first step.

2

Option 2 — Webhook (GitHub event)

Any push, PR, or configured event on the repo fires the pipeline automatically.

3

Option 3 — Manual trigger on GitHub Actions step

Requires workflow_dispatch in your YAML:

yaml

on:
  workflow_dispatch:

Then trigger directly from the GHA step in Opsera.

4

Option 4 — Dynamic parameters at runtime

Useful when you need to change settings without touching the pipeline config.

1. Go to pipeline → Edit Workflow

2. Click the gear icon on Start of Workflow

3. Open Dynamic Settings tab → enable toggle

4. Enable Show Advanced Start Options Screen

5. Enable Show Pipeline Parameters → Save

On next run, click Start Pipeline → pick your parameter overrides from the Pipeline Parameters tab.

Pipeline type must be set to Software Development Life Cycle (SDLC) in the pipeline summary view for dynamic settings to work.

Viewing logs & results

After a run, go to Pipeline Summary tab → scroll to Pipeline Logs → click any Action Summary row.

Tab	What you'll find
Insights	Run number, avg duration, GitHub config details
Summary	Steps executed, status, associated details
Job Logs	Real-time streamed output per step — commands, errors, debug info
Raw Output	Full logs in JSON format

AI analysis (Hummingbird AI)

Opsera's AI layer reads your pipeline run and surfaces:

• Configuration issues

• Error root causes

• Rule or compliance violations

To access: Open a pipeline → click Hummingbird AI tab from the top menu.

FAQs

Can I migrate from Jenkins or Bamboo? Yes. Opsera has AI-powered migration assistants to move existing pipelines to GitHub Actions with minimal manual effort.

How does security work? Opsera layers its own compliance monitoring and security dashboards on top of GitHub's native scanning and code review features — so you catch risks before deployment.

Can non-devs access pipeline status? Yes. Everyone from devs to DevOps to leadership gets the same real-time dashboard, workflow status, and security insights from one platform.

What if my webhook isn't firing? Make sure the webhook was registered on the pipeline before you configured the GitHub Actions step. Re-register from the step settings if needed.

Can I run different workflows per environment? Yes — configure separate pipeline steps (or pipelines) with environment-specific branches and workflows (e.g., staging, production).