Ephemeral Shouldn't Mean Downloading ffmpeg Again

Описание и применение

Повторное скачивание и компиляция ffmpeg для каждой новой среды приводит к избыточным затратам. Внедрение кэширования Tool Shed, основанного на хешах входных данных, позволяет использовать один и тот же артефакт для всех сред, экономя время и ресурсы, но открывает вопросы безопасности и конфиденциальности.

Задача

Repeatedly downloading and compiling the same ffmpeg for each fresh Bench or Workshop wastes time and bandwidth.

Результат

ffmpeg is built once and reused across all Benches and Workshops, saving time and bandwidth while maintaining recipe authority.

Рабочий процесс

• Define ffmpeg build as a recipe step with pinned package set and network profile.
• Compute a hash key from recipe inputs and sealed base.
• Check Tool Shed for existing bytes matching the key.
• If present, reuse cached artifact; if not, derive ffmpeg, store bytes in Tool Shed, and hand over environment.
• Launch Bench or Workshop using the ready environment without exposing the derivation path to the agent.
• Ensure supervisor verifies that all Tool Shed bytes originate from verified recipe executions.
• Delete or purge Tool Shed when desired without affecting recipe authority.

Доказательства

Ten Benches that all need ffmpeg means ten identical downloads and ten identical builds.

Источник

The Tool Shed is where the derived bytes live. It is content-addressed.

Источник

A hash is identity, not safety.

Источник