تشغيل أي مهارة في Manus بنقرة واحدة

$pwd:

adding-tools-to-image

Name: Adding Tools To Image
Author: konflux-ci

// Use when adding new tools, binaries, or packages to the konflux-test container image. Covers artifacts.lock.yaml (generic binaries), rpms.in.yaml (system packages), multi-architecture support, and hermetic build constraints.

تشغيل في Manus

$ git log --oneline --stat

stars:٦

forks:٣٧

updated:٢٦ مايو ٢٠٢٦ في ١٠:٠٢

SKILL.md

readonly

name	adding-tools-to-image
description	Use when adding new tools, binaries, or packages to the konflux-test container image. Covers artifacts.lock.yaml (generic binaries), rpms.in.yaml (system packages), multi-architecture support, and hermetic build constraints.

Adding Tools to the Image

Overview

The konflux-test container image contains 40+ tools and binaries for Konflux CI Tekton tasks. Adding a new tool requires updates to three files due to hermetic build constraints and multi-architecture support.

When to Use

Adding a new binary/utility to the image
Adding a system package via dnf
Updating tool versions
Supporting a new architecture

Quick Reference

Dependency type	Declaration file	Lockfile	Dockerfile
System packages (RPM)	`rpms.in.yaml`	`rpms.lock.yaml`	`dnf install ...`
Binaries/artifacts	`artifacts.lock.yaml`	N/A	`COPY ${PATH_TO_ART}/...`

Adding an RPM Package

Edit rpms.in.yaml — add package name to the packages: list
Regenerate lockfile — cachi2 generates rpms.lock.yaml with pinned versions and checksums
Edit Dockerfile — add dnf install command in the build stage
Verify in CI — CI validates the package installs correctly in hermetic build

Example:

# rpms.in.yaml
packages:
  - jq
  - python3
  - new-package-name  # Add here

Adding a Binary/Artifact

Get download URL and checksum (sha256) for both architectures
Edit artifacts.lock.yaml — add entry with URL, checksum, filename for amd64 AND arm64
Edit Dockerfile — add conditional COPY with $TARGETARCH logic
Verify in CI — CI builds for both architectures

Example:

# artifacts.lock.yaml
- download_url: https://github.com/owner/repo/releases/download/v1.2.0/tool-linux-amd64.tar.gz
  checksum: sha256:abc123def456...
  filename: tool-amd64.tar.gz
- download_url: https://github.com/owner/repo/releases/download/v1.2.0/tool-linux-arm64.tar.gz
  checksum: sha256:def456abc123...
  filename: tool-arm64.tar.gz

Dockerfile pattern:

FROM ubi9/ubi:9.7 AS final

ARG TARGETARCH

RUN if [ "$TARGETARCH" = "amd64" ]; then \
      cp ${PATH_TO_ART}/tool-amd64.tar.gz /tmp/ && \
      tar xzf /tmp/tool-amd64.tar.gz -C /usr/local/bin; \
    elif [ "$TARGETARCH" = "arm64" ]; then \
      cp ${PATH_TO_ART}/tool-arm64.tar.gz /tmp/ && \
      tar xzf /tmp/tool-arm64.tar.gz -C /usr/local/bin; \
    fi

The PATH_TO_ART variable is set by hermetic build system (=/cachi2/output/deps/generic).

Hermetic Build Constraints

Critical: All dependencies must be declared BEFORE build starts — no network access during build.

RPM packages: declared in rpms.in.yaml, locked in rpms.lock.yaml
Generic artifacts: declared in artifacts.lock.yaml with checksums
Cachi2: prefetches all dependencies offline before build
Multi-arch: every binary must have both amd64 and arm64 variants with separate checksums

If a tool is missing from either lockfile, the hermetic build will fail: ERROR: dependency not found.

Multi-Architecture Support

The build system uses TARGETARCH (set by buildkit) to select architecture-specific binaries:

ARG TARGETARCH
RUN if [ "$TARGETARCH" = "amd64" ]; then copy-amd64; \
    elif [ "$TARGETARCH" = "arm64" ]; then copy-arm64; \
    fi

Every multi-arch binary in artifacts.lock.yaml needs BOTH amd64 and arm64 entries with separate checksums.

Multiple Versions

Tools like opm are intentionally installed at multiple versions for backwards compatibility with different OCP versions (v1.26.4 through v1.57.0). Each version is a separate artifact entry.

Validating the Tool

After adding a tool, test/selftest.sh should validate:

Binary is present and executable
Binary returns expected version/help output
Binary works correctly in integration tests

Add a validation check to test/selftest.sh:

if ! command -v new-tool &> /dev/null; then
    echo "ERROR: new-tool not found in image"
    exit 1
fi

Common Mistakes

Mistake	Fix
Missing from artifacts.lock.yaml	Add entry with download_url, checksum, filename (both arches)
Only amd64 variant, missing arm64	Every binary needs both variants with separate checksums
Wrong checksum format	Use `sha256:` prefix and full hash (not abbreviated)
Dockerfile COPY wrong path	Use `${PATH_TO_ART}/filename` (=/cachi2/output/deps/generic)
Dockerfile forgot $TARGETARCH condition	Both amd64 and arm64 builds will fail with "file not found"
Tool not validated in selftest.sh	Add `command -v tool` check and version validation

related-skills.json

نفس المستودع

ci-cd-quirks.md

from "konflux-ci/konflux-test"

Use when CI checks fail unexpectedly, when preparing code for CI, or when encountering non-obvious build and pipeline behavior. Covers hermetic builds, Tekton pipelines, multi-arch, GitHub Actions checks, and integration test structure.

2026-05-266

pr-definition-of-done.md

from "konflux-ci/konflux-test"

Use when preparing a pull request for review or before pushing. Checklist of commit conventions, Rego policy tests at 100% coverage, BATS tests, code quality checks, and CI check requirements.

2026-05-266

running-tests-locally.md

from "konflux-ci/konflux-test"

Use when running OPA policy unit tests, BATS bash tests, shellcheck, hadolint, or conftest integration tests locally. Covers test commands, coverage requirements, test data, and prerequisites.

2026-05-266

writing-bash-functions.md

from "konflux-ci/konflux-test"

Use when adding or modifying bash utility functions in test/utils.sh. Covers naming conventions, function structure, BATS tests, mock patterns for external tools, TEST_OUTPUT format, and shellcheck compliance.

2026-05-266

writing-rego-policies.md

from "konflux-ci/konflux-test"

Use when writing, modifying, or reviewing OPA/conftest Rego policies. Covers package naming, rule prefixes (violation_ and warn_), conftest namespaces, violation object structures, imports, and unit test patterns.

2026-05-266

package.json

"author": "konflux-ci"

"repository": "konflux-ci/konflux-test"

فتح مستودع GitHub عرض مستودعات المنشئ

$ install --global

$ download --local

تشغيل في Manus

$ useful --forSOC

مطوّرو البرمجياتمهن الحاسوب والرياضيات15-1252L4

name	adding-tools-to-image
description	Use when adding new tools, binaries, or packages to the konflux-test container image. Covers artifacts.lock.yaml (generic binaries), rpms.in.yaml (system packages), multi-architecture support, and hermetic build constraints.

Adding Tools to the Image

Overview

When to Use

Adding a new binary/utility to the image
Adding a system package via dnf
Updating tool versions
Supporting a new architecture

Quick Reference

Dependency type	Declaration file	Lockfile	Dockerfile
System packages (RPM)	`rpms.in.yaml`	`rpms.lock.yaml`	`dnf install ...`
Binaries/artifacts	`artifacts.lock.yaml`	N/A	`COPY ${PATH_TO_ART}/...`

Adding an RPM Package

Edit rpms.in.yaml — add package name to the packages: list
Regenerate lockfile — cachi2 generates rpms.lock.yaml with pinned versions and checksums
Edit Dockerfile — add dnf install command in the build stage
Verify in CI — CI validates the package installs correctly in hermetic build

Example:

# rpms.in.yaml
packages:
  - jq
  - python3
  - new-package-name  # Add here

Adding a Binary/Artifact

Get download URL and checksum (sha256) for both architectures
Edit artifacts.lock.yaml — add entry with URL, checksum, filename for amd64 AND arm64
Edit Dockerfile — add conditional COPY with $TARGETARCH logic
Verify in CI — CI builds for both architectures

Example:

# artifacts.lock.yaml
- download_url: https://github.com/owner/repo/releases/download/v1.2.0/tool-linux-amd64.tar.gz
  checksum: sha256:abc123def456...
  filename: tool-amd64.tar.gz
- download_url: https://github.com/owner/repo/releases/download/v1.2.0/tool-linux-arm64.tar.gz
  checksum: sha256:def456abc123...
  filename: tool-arm64.tar.gz

Dockerfile pattern:

FROM ubi9/ubi:9.7 AS final

ARG TARGETARCH

RUN if [ "$TARGETARCH" = "amd64" ]; then \
      cp ${PATH_TO_ART}/tool-amd64.tar.gz /tmp/ && \
      tar xzf /tmp/tool-amd64.tar.gz -C /usr/local/bin; \
    elif [ "$TARGETARCH" = "arm64" ]; then \
      cp ${PATH_TO_ART}/tool-arm64.tar.gz /tmp/ && \
      tar xzf /tmp/tool-arm64.tar.gz -C /usr/local/bin; \
    fi

The PATH_TO_ART variable is set by hermetic build system (=/cachi2/output/deps/generic).

Hermetic Build Constraints

Critical: All dependencies must be declared BEFORE build starts — no network access during build.

RPM packages: declared in rpms.in.yaml, locked in rpms.lock.yaml
Generic artifacts: declared in artifacts.lock.yaml with checksums
Cachi2: prefetches all dependencies offline before build
Multi-arch: every binary must have both amd64 and arm64 variants with separate checksums

If a tool is missing from either lockfile, the hermetic build will fail: ERROR: dependency not found.

Multi-Architecture Support

The build system uses TARGETARCH (set by buildkit) to select architecture-specific binaries:

ARG TARGETARCH
RUN if [ "$TARGETARCH" = "amd64" ]; then copy-amd64; \
    elif [ "$TARGETARCH" = "arm64" ]; then copy-arm64; \
    fi

Every multi-arch binary in artifacts.lock.yaml needs BOTH amd64 and arm64 entries with separate checksums.

Multiple Versions

Tools like opm are intentionally installed at multiple versions for backwards compatibility with different OCP versions (v1.26.4 through v1.57.0). Each version is a separate artifact entry.

Validating the Tool

After adding a tool, test/selftest.sh should validate:

Binary is present and executable
Binary returns expected version/help output
Binary works correctly in integration tests

Add a validation check to test/selftest.sh:

if ! command -v new-tool &> /dev/null; then
    echo "ERROR: new-tool not found in image"
    exit 1
fi

Common Mistakes

Mistake	Fix
Missing from artifacts.lock.yaml	Add entry with download_url, checksum, filename (both arches)
Only amd64 variant, missing arm64	Every binary needs both variants with separate checksums
Wrong checksum format	Use `sha256:` prefix and full hash (not abbreviated)
Dockerfile COPY wrong path	Use `${PATH_TO_ART}/filename` (=/cachi2/output/deps/generic)
Dockerfile forgot $TARGETARCH condition	Both amd64 and arm64 builds will fail with "file not found"
Tool not validated in selftest.sh	Add `command -v tool` check and version validation

adding-tools-to-image

Adding Tools to the Image

Overview

When to Use

Quick Reference

Adding an RPM Package

Adding a Binary/Artifact

Hermetic Build Constraints

Multi-Architecture Support

Multiple Versions

Validating the Tool

Common Mistakes

المزيد من هذا المستودع

المزيد من هذا المستودع

Adding Tools to the Image

Overview

When to Use

Quick Reference

Adding an RPM Package

Adding a Binary/Artifact

Hermetic Build Constraints

Multi-Architecture Support

Multiple Versions

Validating the Tool

Common Mistakes