rsyslog_local_container_testing

Validate rsyslog changes locally using containers and static analysis tools.

2.3k|728|Updated Jun 3, 2013
One-click install
npx skills add https://github.com/rsyslog/rsyslog --skill rsyslog-local-container-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rsyslog_local_container_testing
Source: https://github.com/rsyslog/rsyslog/tree/main/.agent/skills/rsyslog_local_container_testing
Command: npx skills add https://github.com/rsyslog/rsyslog --skill rsyslog-local-container-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, podman, clang, gcc, scan-build, valgrind, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill enables local container testing of rsyslog changes, allowing developers to catch potential issues before they reach the CI environment.

Core Features & Use Cases

  • Local Container Testing: Mirror container validation for rsyslog changes locally.
  • PR-Ready Validation: Provides a set of checks for PR validation, including static analysis and Ubuntu 26.04 container checks.
  • Use Case: When working on a pull request for rsyslog, this Skill can be used to perform local validation, catching issues such as static analysis failures or containerization problems early in the development process.

Quick Start

To run local container validation for your rsyslog changes, use the following command:

devtools/local-validation-plan.sh --run

Frequently Asked Questions about rsyslog_local_container_testing

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

FAQPage Schema
How do I validate rsyslog changes locally before submitting a pull request?

You can validate rsyslog changes locally by running container testing scripts like `devtools/local-validation-plan.sh --run` to mirror CI checks and catch static analysis or containerization issues early.

What container tools are needed to run local rsyslog validation?

Local rsyslog validation requires containerization tools like Docker or Podman to execute the container testing checks and validate code changes effectively.

Does local container testing for rsyslog include static analysis?

Yes, local container testing for rsyslog includes static analysis using tools like scan-build, clang, and gcc to ensure code quality and identify potential vulnerabilities before PR submission.

What is the best way to mirror CI pipeline checks for rsyslog on my local machine?

The best way to mirror CI pipeline checks locally is using rsyslog container testing scripts to reproduce Ubuntu container checks and static analysis validations before pushing code.

Can I use valgrind for local rsyslog code validation in containers?

Yes, valgrind is utilized alongside other tools in the local container testing suite to perform memory debugging and static analysis on rsyslog code changes.

Why does my rsyslog pull request fail CI checks but pass local builds?

Local builds may miss CI failures because they lack the exact Ubuntu container environment and static analysis suite; using local container testing scripts mirrors the CI environment to catch these issues.