add-linux-bootstrap-platform

Automate adding Linux distros as ponyup bootstrap-test targets across CI workflows.

218|14|Updated May 6, 2017
One-click install
npx skills add https://github.com/ponylang/ponyup --skill add-linux-bootstrap-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-linux-bootstrap-platform
Source: https://github.com/ponylang/ponyup/tree/main/.claude/skills/add-linux-bootstrap-platform
Command: npx skills add https://github.com/ponylang/ponyup --skill add-linux-bootstrap-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of adding a new Linux distro/version as a ponyup bootstrap-test target, including multi-arch bootstrap-tester scaffolding, CI integration, and release-note generation.

Core Features & Use Cases

  • Sets up a bootstrap-tester pipeline for a new distro/version (arm64 and amd64) with a multi-arch Dockerfile and build-push script.
  • Updates CI workflows (pr.yml and ponyup-tier2.yml) and ponyup-init.sh detection to recognize the new platform.
  • Creates a release note and adjusts canonical example strings and tests as needed.

Quick Start

Follow the steps in the skill's instructions to scaffold the bootstrap-tester, integrate with CI, and update ponyup-init.sh detection.

Frequently Asked Questions about add-linux-bootstrap-platform

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

FAQPage Schema
How do I add a new Linux distro as a ponyup bootstrap-test target?

Adding a new Linux distro as a ponyup bootstrap-test target requires scaffolding a multi-arch Dockerfile, updating CI workflows like pr.yml and tier2.yml, and modifying ponyup-init.sh distro detection to recognize the new platform.

Does the ponyup bootstrap-tester support multi-arch Docker builds for Alpine and Ubuntu?

Yes, the ponyup bootstrap-tester supports multi-arch Docker builds for both arm64 and amd64 architectures, specifically applying to Alpine and Ubuntu Linux distribution families.

What CI workflows need updating when adding a new Linux bootstrap platform?

Adding a new Linux bootstrap platform requires updating the pr.yml and ponyup-tier2.yml CI workflows, alongside creating a build-and-push.bash script in the .ci-dockerfiles directory to coordinate Docker image pushes.

How do I update ponyup-init.sh to detect a new Linux distribution?

Updating ponyup-init.sh to detect a new Linux distribution involves adding logic that recognizes the new distro and version, ensuring the bootstrap-tester pipeline correctly targets the platform during installation.

Do I need to create release notes when adding a bootstrap-test target?

Yes, creating release notes is required when adding a bootstrap-test target, documenting the new Linux distro support and adjusting canonical example strings and tests as needed.

What is the best way to scaffold a multi-arch bootstrap-tester for a new Linux version?

The best way to scaffold a multi-arch bootstrap-tester is creating a .ci-dockerfiles/<distro><version>-bootstrap-tester directory containing a Dockerfile and build-and-push.bash, then integrating CI workflows and release notes.