Ability to prevent a step from downloading artifacts

Issue #16728 open
Nick Phillips created an issue

Might help save a few CPU cycles and build time.

Basically we have a few builds where only 2 of the 5 steps require the artifacts, would be nice if you could add a flag to disable these.

Source: https://twitter.com/jeroendra/status/1019829831377170432

Comments (9)

  1. Aneita Yang staff
    • changed status to open

    Hey @Nick Phillips,

    Thanks for reaching out and for the suggestion - I can see why this is something that you're interested in.

    We're currently working on higher priority projects and don't have any plans to work on this anytime soon. In the meantime, I'll open this issue to see whether other users are interested in seeing the same thing

    Aneita

  2. Aneita Yang staff

    I understood this request as being able to specify whether a step should download artifacts from a previous step. I understood issue #16628 to be around specifying whether the repository should be cloned at all. Please let me know if I am misunderstanding these 2 issues.

  3. Aneita Yang staff

    Thanks @ZenobiusJ. I'm going to leave these as 2 separate requests as I do think they solve different use cases.

    @Nick Phillips, perhaps you can elaborate on what steps you have within your pipeline that don't require any artifacts.

  4. Nick Phillips reporter

    I don't think they are the same issue. I still would need a git clone, just none of the artifacts from previous steps.

    My use case (simplified):

    • Parallel Step 1 - Build front end code using NodeJS image
    • Parallel Step 2 - Download PHP vendors with composer using custom PHP image
    • Step 3 - Build back end image baked with artifacts from Step 1 and 2
    • Step 4 - Create AWS task definitions, push event notifications than a new tagged release is coming etc. None of which needs the previous artifacts, but does use files within the repository.
  5. Thomas Raehalme

    I would prefer if each step would define what the step wants to publish as artifacts for the next step. If nothing, artifacts are cleared.

    In addition to speeding up subsequent steps this would also help with the problem of artifacts expiring before a manual step is run.

    My use case is that we build the project in the first step which publishes the result as an artifact. The second step then uses the artifact to build a Docker image. Subsequent steps no longer need the original artifact so the second step does not publish anything.

  6. Log in to comment