Coordinates cross-repo development, testing, and packaging of AlwaysOn infrastructure in NitroUMDP.
npx skills add https://github.com/huangcd/gcusage --skill alwayson-dev
Please help me install this Agent Skill. Skill: alwayson-dev Source: https://github.com/huangcd/gcusage/tree/main/.github/skills/alwayson-dev Command: npx skills add https://github.com/huangcd/gcusage --skill alwayson-dev
This Skill centralizes and standardizes the development and testing workflow for the AlwaysOn infrastructure components, enabling teams to coordinate cross-repo changes safely and efficiently.
Modify AlwaysOn infra in sources/dev/AlwaysOn/infra/src and run the local refresh to test changes in NitroUMDP.
High-intent search queries and answers about installing and using this skill.
Cross-repo infrastructure changes across NitroUMDP environments are coordinated by standardizing the development workflow for pipeline builders and ScopeConnectors. This process ensures consistent builds and safe cross-repo validation across NitroUMDP and NitroUMDPProductUsage.
The local refresh workflow for AlwaysOn infrastructure packages involves modifying infra code in sources/dev/AlwaysOn/infra/src and validating changes in consumer workspaces. This process verifies consumer workspace integration before broader releases.
Yes, developing AlwaysOn infrastructure components requires working knowledge of the AlwaysOn infra packaging process, local refresh script usage, and consumer workspace integration. This expertise ensures consistent builds and safe cross-repo validation.
To bump local versions and package the AlwaysOn infra library, follow the package build and test orchestration steps to update versions, package the library, and verify consumer workspace integration. This validates changes before broader releases.
Yes, this workflow facilitates changes to standard dimensions and pipeline builders across both NitroUMDP and NitroUMDPProductUsage environments. It applies to infra code requiring cross-repo validation to ensure consistent builds.
AlwaysOn infrastructure packaging requires validation in consumer workspaces to verify local refresh workflows and ensure consistent builds. This local testing step catches integration issues before broader releases are deployed.
synqingCreate isolated git worktrees for feature branches with dependency setup and baseline testing.
Generous-CorpAutomate build verification, dependency pin updates, and release runbook generation for Pulp SDK consumer repositories.
CalmKernelTRAutomate cross-distro package builds and validation for AUR, Alpine APK, and RPM.
8DionysusApply the aoa-safe-infra-change workflow to abyss-* repositories with rollback and verification commands.
