cicd

Document local builds, Docker images, and GitHub Actions CI/CD workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Pandaala/Edgion --skill cicd-pandaala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd
Source: https://github.com/Pandaala/Edgion/tree/main/skills/09-misc/cicd
Command: npx skills add https://github.com/Pandaala/Edgion --skill cicd-pandaala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Edgion contributors and release engineers need a reliable way to build locally, package correct binaries into Docker images, and understand what the CI/CD pipelines do—so builds don’t break unexpectedly and releases publish the right artifacts.

Core Features & Use Cases

  • Local build guidance: choose build commands, required tooling (like protoc), build outputs, feature combinations (allocator and TLS backend), and diagnose common failure modes.
  • Docker build workflow: understand multi-stage Dockerfiles, cargo-chef caching, build arguments, and when to use the source-build image vs runtime packaging image.
  • CI/CD and release transparency: map GitHub Actions job flow, caching behavior, multi-arch release binary builds, Docker image publishing, manifest merging, and release note publishing conventions.

Quick Start

Run the GitHub Actions workflow reproduction steps to mirror CI and confirm your change won’t fail during check, test, or release packaging.

Frequently Asked Questions about cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure GitHub Actions for multi-architecture Docker builds?

Configure GitHub Actions for multi-architecture Docker builds by mapping job flows, managing manifest merging, and coordinating caching to publish correct release binaries across different architectures.

What is cargo-chef caching and when do I use it in a Rust build workflow?

Cargo-chef caching is a Docker multi-stage build mechanism used to cache Rust dependencies, speeding up local debugging and CI image construction by separating dependency compilation from source building.

How do I build and test Rust feature combinations like allocator and TLS backend locally?

Build Rust feature combinations locally by selecting exact build commands, installing required tooling like protoc, and validating specific feature flags to reproduce CI checks before pushing changes.

Do I need protoc to build and ship Docker images using GitHub Actions CI/CD?

Yes, protoc is a required prerequisite tooling dependency for building and shipping correctly, ensuring local build paths and CI pipelines generate expected artifacts without unexpected failures.

What is the best way to diagnose CI/CD pipeline failures during release publishing?

Diagnose CI/CD release publishing failures by reviewing GitHub Actions workflow definitions, checking multi-arch binary build stages, and verifying release note conventions and image publishing behavior.

When should I use a source-build image vs a runtime packaging image for Docker builds?

Use a source-build image to compile binaries with specific build arguments and feature combinations, while a runtime packaging image stages the compiled artifacts for final multi-architecture distribution.