ykohut/leapp-repository
1
0
Fork 0
forked from rpms/leapp-repository
Code Pull Requests Activity

We don't keep any AI skills in the project.

Browse Source
This commit is contained in:
Yuriy Kohut 2026-04-23 11:48:14 +03:00
parent ed3d973ab5
commit c8b7636940
1 changed files with 0 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

72
.claude/skills/build-and-sign/SKILL.md
View File

@ -1,72 +0,0 @@
---
name: build-and-sign
description: >-
Build and sign packages on ALBS (AlmaLinux Build System) using the albs-mcp
MCP server. Use when the user asks to build, rebuild, or sign packages, or
mentions ALBS builds, or package signing.
---
# Build and Sign Packages
Build leapp-repository on ALBS for AlmaLinux-8 and AlmaLinux-9, then sign
completed builds with the ELevate key.
## Prerequisites
- The `albs-mcp` MCP server must be running (configured in `.cursor/mcp.json`).
- A valid JWT token must be configured for authenticated operations.
## Workflow
### Step 1: Determine the branch
Get the current git branch to use as the build ref:
```bash
git rev-parse --abbrev-ref HEAD
```
The user may override the branch explicitly. If not, use the current branch.
### Step 2: Create the build
Call `create_build` via the `albs-mcp` MCP server **once** with both platforms:
| Parameter | Value |
|-------------|----------------------|
| packages | `["leapp-repository"]` |
| platforms | `["AlmaLinux-8", "AlmaLinux-9"]` |
| branch | current git branch (from Step 1) |
| arch_list | `["x86_64"]` |
This creates a single build containing tasks for both platforms. Record the returned **build ID**.
### Step 3: Wait for the build to complete
Poll the build with `get_build_info` until all tasks show `completed` or `failed`.
Use exponential backoff: start at 60 seconds, increase up to 5 minutes between checks.
If any task **fails**, report the failure to the user and ask whether to proceed
with signing or investigate the failure.
### Step 4: Sign the completed build
Call `sign_build` with:
| Parameter | Value |
|-------------|-------|
| build_id | the build ID from Step 2 |
| sign_key_id | `3` (ELevate key) |
### Step 5: Report results
Present a summary:
```
Build ID: <id>
URL: https://build.almalinux.org/build/<id>
Platforms: AlmaLinux-8, AlmaLinux-9
Build Status: completed
Sign Task ID: <sign_id>
Sign Status: idle
```