Skip to content
@kettle-dev

kettle-dev

Development & testing harnesses

kettle-dev

kettle-dev is a family of Ruby tooling gems for maintaining RubyGems with a consistent development, test, coverage, CI, release, and templating workflow.

The organization was previously named kettle-rb. Older references to kettle-rb/* are historical; current Kettle tooling lives under kettle-dev/*.

What Lives Here

Development and Release Tooling

Project Purpose
kettle-dev Rake tasks and CLIs for RubyGem development, changelogs, pre-release checks, release automation, documentation, and CI helpers.
kettle-family Coordinates install, template, state, reset, bump, and release operations across related RubyGem repositories.
kettle-rb Shared Ruby, engine, Rails, RuboCop, and RuboCop LTS compatibility matrix data used by Kettle-managed gems.
nomono ENV-driven Gemfile macros for resolving local sibling gems during multi-repo development.

Testing, Coverage, and Quality

Project Purpose
kettle-test RSpec test harness and helper bundle for Kettle-managed gems.
kettle-soup-cover SimpleCov configuration and coverage reporting for local runs and CI providers.
kettle-gha-pins GitHub Actions SHA pin discovery, validation, cache-backed resolution, and upgrade planning.
kettle-drift Detects repeated adjacent-line chunks that usually indicate template drift or copy/paste corruption.
kettle-wash Constant deletion and reset helpers for repeatable reload-oriented tests.

Shared CLI and Template Primitives

Project Purpose
kettle-ndjson NDJSON event stream primitives, filters, recorders, and payload helpers for Kettle CLIs.
token-resolver PEG-based token parsing and replacement for template pipelines.

Related Project: StructuredMerge

The AST and structured merge gems that used to be separate repositories under the old kettle-rb organization now live in the structuredmerge-ruby monorepo.

That includes projects such as tree_haver, ast-merge, prism-merge, markdown-merge, markly-merge, toml-merge, yaml-merge, and kettle-jem. Kettle still uses that toolchain, but those repositories are no longer part of this organization profile.

Typical Workflow

Kettle-managed gems usually combine:

  • kettle-test for RSpec execution and test helpers.
  • kettle-soup-cover for coverage setup and reports.
  • kettle-dev for Rake tasks, changelog generation, pre-release checks, and release orchestration.
  • kettle-family when a set of related gems needs to be installed, templated, reset, bumped, or released as a dependency-ordered group.
  • nomono for switching between released gems and local sibling paths without hand-editing Gemfiles.

Package Source

Kettle gems are published as RubyGems. Kettle-managed projects commonly use https://gem.coop as the Bundler source, which proxies RubyGems.org for normal Bundler installs.

Pinned Loading

  1. kettle-soup-cover kettle-soup-cover Public

    🥘 A Covered Kettle of SOUP, A Code Coverage Meta Gem

    Ruby 10 1

  2. kettle-dev kettle-dev Public

    🍲 Setup a complete rake & dev harness for Ruby development; tasks for coverage, GHA console, linting, debugging, etc.

    Ruby 2

  3. kettle-test kettle-test Public

    🍲 Setup a complete multi-core parallelized RSpec test harness, temporal manipulation, silent output testing, block expectations, etc.

    Ruby 2

  4. token-resolver token-resolver Public

    🪙 Configurable PEG-based token parser and resolver for structured token detection and replacement in arbitrary text

    Ruby 4

  5. kettle-wash kettle-wash Public

    🚿 Runner up name: "constant_change". A gem for your test / spec harness providing a pattern for resetting constants; Enable simpler testing, and consistent deterministic results.

    Ruby 1

  6. nomono nomono Public

    1️⃣ Q: When is a Monorepo not A Monorepo? A: When it is a nomono. Just a bunch of repos in the same directory.

    Ruby 1

Repositories

Showing 10 of 17 repositories

Top languages

Loading…

Most used topics

Loading…