proomt

Search

Search posts, papers, and topics

All posts

Codeship1 min readintermediate

Copying Artifacts Between Builds in a Jenkins Workflow

Read on cloudbees.com

Summary

The copyartifact plugin now supports Jenkins Pipeline via a core step (v1.34). Use the generic `step([$class: 'CopyArtifact', …])` syntax to pull artifacts from another job, with all existing options available through the Snippet Generator. A native pipeline step is planned.

  • CopyArtifact can be invoked in Declarative/Scripted Pipelines using the generic `step` syntax.
  • All existing plugin options (filters, project name, etc.) are still supported.
  • The Snippet Generator in the Pipeline UI is the easiest way to discover the correct syntax.
  • Future work aims to expose a dedicated pipeline step for copyartifact.

Artifact sharing between jobs is a common pattern in CI/CD. Being able to do it directly in Pipeline code removes the need for ad‑hoc shell scripts or separate freestyle jobs, keeping the build definition declarative and version‑controlled.

4/10
devopsautomationci cdpluginsjenkinspipeline

Related reading

  3. Building a Reliable Script-to-Video Pipeline for Modern Web Applications

    A practical guide to building a reliable, observable script‑to‑video pipeline. It advocates a staged architecture (scene manifest → asset generation → voice → rendering → encoding), validates AI‑generated JSON with Zod, persists project and scene state, uses explicit workflow states, runs heavy work in background queues, limits concurrency, and stores voice, captions, and assets separately to ena…

    SitePointsitepoint.com11 min

  6. How to Write with an LLM

    The post proposes a two‑rule workflow for using LLMs as copy‑editors rather than ghostwriters: never adopt a phrase the model suggests, and block its encouragement feedback. It then shows how to automate iterative copy‑editing with a small Python/HTMX/Tailwind app and a set of concrete prompts.

    Hacker News front pagesockpuppet.org6 minHN712401