Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,895
    • Issues 34,895
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,229
    • Merge Requests 1,229
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #201784

Closed
Open
Opened Feb 03, 2020 by Chris Weyl@rsrchboy

Child pipeline artifacts cannot be downloaded via ref-based links

Summary

Artifacts from jobs in child pipelines cannot be downloaded via the instructions in the docs, e.g.:

https://gitlab.com/rsrchboy/scratch/-/jobs/artifacts/child-artifacts/raw/admiralty.txt\?job\=build-child

Steps to reproduce

  1. Create a child pipeline containing a job that generates artifacts.
  2. Attempt to download artifact from the "child job".

Example Project

I've created a scratch repo/pipeline to demonstrate this:

https://gitlab.com/rsrchboy/scratch/commits/child-artifacts

The parent and child pipelines both contain jobs that generate artifacts.

What is the current bug behavior?

The latest artifacts from the job in the parent pipeline can be downloaded, e.g.:

$ curl --location https://gitlab.com/rsrchboy/scratch/-/jobs/artifacts/child-artifacts/raw/artifacty\?job\=build-parent
I am the model of a modern major general

...while they cannot from the child pipeline:

$ curl -v https://gitlab.com/rsrchboy/scratch/-/jobs/artifacts/child-artifacts/raw/admiralty.txt\?job\=build-child
<...snip...>
> GET /rsrchboy/scratch/-/jobs/artifacts/child-artifacts/raw/admiralty.txt?job=build-child HTTP/1.1
> Host: gitlab.com
> User-Agent: curl/7.67.0
> Accept: */*
<...snip...>
< HTTP/1.1 404 Not Found
<...snip...>

What is the expected correct behavior?

I'd expect the artifact from the child job to be fetched in the same fashion as the artifact in the parent job:

$ curl --location https://gitlab.com/rsrchboy/scratch/-/jobs/artifacts/child-artifacts/raw/admiralty.txt\?job\=build-child
I am the monarch of the sea

Relevant logs and/or screenshots

Logs, etc, can all be found in the pipelines at:

  • https://gitlab.com/rsrchboy/scratch/commits/child-artifacts
  • rsrchboy/scratch@2aeb1b7b
  • https://gitlab.com/rsrchboy/scratch/pipelines/114604557

Output of checks

This bug happens on GitLab.com.

Proposal

There is a proposal MR !29710 (merged) that describes the direction we can take to solve this problem. It needs to be completed.

Edited Apr 23, 2020 by Fabio Pitino
Assignee
Assign to
13.5
Milestone
13.5 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#201784