Automation
67 items tagged with "automation"
Standards2
OPC UA 1.05
Understanding the OPC standard is essential for successful software migrations in industrial automation. By ensuring compliance with this standard, teams can enhance interoperability, reduce risks, and meet regulatory requirements. Effective planning, appropriate tools, and addressing common challenges are key to a seamless migration experience.
CBL-Mariner OS Spec 2.0
Adhering to Microsoft's migration standards is essential for ensuring data integrity, security, and compliance during software migrations. By following established guidelines, teams can mitigate risks, meet regulatory requirements, and enhance collaboration. Implementing automated tools and a structured approach will facilitate a smooth transition, while addressing common challenges can further optimize the process.
Best Practices16
CALMS DevOps Principles
Framework emphasising Culture, Automation, Lean, Measurement, and Sharing as pillars of DevOps success.
GitOps Principles v1
Declarative, verifiable and automated operations — using Git as the single source of truth for infra and apps.
Continuous Integration Best Practices
A development practice where engineers merge code into a shared mainline many times a day, each merge verified by an automated build and test suite.
Continuous Delivery
A discipline where software is built so it can be released to production safely at any time, with every change proven release-ready by an automated pipeline.
Deployment Pipeline Pattern
An automated, staged path that takes every code change from commit through build, tests, and successive environments, providing a single auditable route to production.
GitHub Flow
A lightweight, branch-based workflow built around short-lived feature branches, pull requests, and continuous deployment from a single always-deployable main branch.
Pipeline as Code
Defining CI/CD pipelines in version-controlled configuration files stored alongside the application, so the delivery process is reviewable, reproducible, and auditable.
Pre-Commit Hooks Automation
Automating checks such as formatting, linting, and secret scanning that run on every Git commit, catching issues locally before they ever reach the shared repository.
Configuration as Code
Managing application and system configuration in version-controlled, machine-readable files instead of manual settings, making configuration reviewable, auditable, and reproducible.
Runbook Automation
Codifying operational procedures as automated, repeatable workflows so common incident responses and maintenance tasks run reliably with less manual toil.
Toil Reduction
Systematically identifying and eliminating repetitive, manual, automatable operational work so engineers can spend time on durable engineering instead.
ELT vs ETL Best Practices
Guidance on when to transform data before loading (ETL) versus loading raw and transforming in the warehouse (ELT), and how to run each pattern well.
Reverse ETL
The practice of moving modeled data from the warehouse back into operational tools like CRM and marketing platforms so business teams act on it directly.
MLOps Principles
The discipline of applying DevOps and engineering rigor to machine learning so models are built, deployed, monitored, and retrained reliably and reproducibly.
Documentation as Code
Documentation as Code treats docs like software: stored in version control, written in plain text, reviewed in pull requests, and published automatically through continuous integration.
Internal Developer Platform
An Internal Developer Platform (IDP) is the self-service product built by platform teams that gives developers golden paths to provision, build, deploy, and operate software with built-in guardrails.
Models2
Tutorials8
CI/CD Pipeline with GitHub Actions
Set up a complete CI/CD pipeline using GitHub Actions
How to build a GitHub Actions pipeline for a web app
Create a complete GitHub Actions workflow that lints, tests, and builds an application on every push and pull request.
How to set up a GitLab CI/CD pipeline
Configure a .gitlab-ci.yml pipeline with stages for testing, building, and deploying using GitLab runners.
How to create a reusable GitHub Actions workflow
Build a callable workflow with inputs and secrets so multiple repositories share one tested CI definition.
How to write an Ansible playbook to configure servers
Build an inventory and an idempotent Ansible playbook to install and configure software across multiple servers.
How to automate versioning and releases with semantic-release
Use semantic-release and Conventional Commits to automatically determine versions, tag releases, and publish from CI.
How to automate dependency updates in CI
Configure automated dependency update pull requests with grouping, scheduling, and auto-merge for safe updates.
How to set up a CircleCI pipeline with workflows
Configure a CircleCI pipeline using jobs, workflows, and orbs to test and deploy an application.
Products9
Python
High-level, interpreted programming language with dynamic semantics
Terraform
Infrastructure as Code tool for building and managing infrastructure
Pulumi
Infrastructure as Code using real programming languages
Ansible
Automation platform for configuration management
Argo CD
Declarative GitOps continuous delivery for Kubernetes
Jenkins
Open source automation server for CI/CD
GitHub Actions
CI/CD platform integrated with GitHub
GitLab CI/CD
Built-in CI/CD for GitLab
CircleCI
Cloud-based CI/CD platform
Playbooks3
DevOps Adoption Playbook
Organization-wide DevOps transformation playbook
CI/CD Modernization Playbook
A phased program to move from manual or brittle pipelines to fast, secure, pipeline-as-code delivery with automated gates.
SOC 2 and ISO 27001 Compliance Automation Playbook
A program to automate evidence collection and control monitoring for SOC 2 and ISO 27001, turning audits into continuous compliance.
Comparisons5
Ansible vs Terraform
Ansible is a configuration-management and automation tool; Terraform is a declarative infrastructure-provisioning tool. They overlap but solve different core problems.
GitHub Actions vs GitLab CI/CD
Both run pipelines defined in YAML next to your code. GitHub Actions centers on a marketplace of reusable actions; GitLab CI/CD ships an integrated DevOps platform.
GitHub Actions vs Jenkins
GitHub Actions is a managed, YAML-driven CI/CD service tied to GitHub; Jenkins is a self-hosted, plugin-rich automation server with maximum flexibility.
CircleCI vs GitHub Actions
CircleCI is a dedicated cloud CI/CD platform known for speed and orbs; GitHub Actions is GitHub's native automation with a huge action marketplace.
Terraform vs Ansible
Terraform is a declarative infrastructure-provisioning tool; Ansible is a procedural configuration-management and automation tool. They solve different DevOps problems.
Generators1
FAQs8
How do I integrate Vibgrate into CI/CD pipelines?
The CLI requires no login for scanning and returns meaningful exit codes (0=success, 2=threshold exceeded). Basic CI integration: npx @vibgrate/cli sc...
What do the CLI exit codes mean?
Exit code 0: Success (scan completed, all gates passed). Exit code 1: Runtime error (invalid flags, missing files, crash). Exit code 2: Threshold exce...
Can I use Vibgrate programmatically in my own code?
Yes. Import types from @vibgrate/cli@latest for type-safe access to scan artifacts: import type { VibgrateConfig, ScanArtifact, DriftScore, Finding } ...
How do I run Vibgrate in Jenkins?
Use node:22 Docker image or ensure Node.js 22+ is installed on agents. Run npx @vibgrate/cli scan --format sarif --out vibgrate.sarif --fail-on error....
What is infrastructure as code?
Infrastructure as code (IaC) is the practice of defining and provisioning infrastructure, such as servers, networks, and databases, through machine-re...
What is an AI agent?
An AI agent is a system that uses a language model to decide and take actions toward a goal, rather than producing a single response. It typically ope...
What is CI/CD?
CI/CD stands for Continuous Integration and Continuous Delivery (or Deployment). Continuous Integration means developers merge code into a shared bran...
What is GitOps?
GitOps is an operational model where the desired state of infrastructure and applications is declared in a Git repository, and an automated controller...
Glossaries9
CI/CD
Continuous Integration and Continuous Deployment - practices for automating code integration and delivery
Infrastructure as Code
Managing and provisioning infrastructure through machine-readable configuration files
Operator Pattern
The Operator pattern is a Kubernetes approach that encodes operational knowledge for a specific application into custom controllers and custom resources, automating tasks like deployment, upgrades, backup, and failover.
AI Agent
An AI agent is a system that uses a language model to plan and take actions toward a goal, calling tools, observing results, and iterating with limited human input.
Continuous Integration (CI)
A practice where developers merge code changes into a shared repository frequently, with each merge automatically built and tested to catch integration problems early.
Continuous Delivery (CD)
A practice where software is kept in a releasable state at all times, with every change automatically built, tested, and prepared for deployment, leaving the final release as a manual decision.
Continuous Deployment
A practice where every change that passes the automated pipeline is released to production automatically, with no manual approval step.
GitOps
An operational model in which the desired state of infrastructure and applications is declared in a Git repository and automatically reconciled into the running environment by an agent.
Toil
Manual, repetitive, automatable operational work that scales linearly with service size and provides no lasting value, a key target for reduction in site reliability engineering.