Skip to content

Allow scheduled pipeline execution policy bot to download artifacts

Summary

Jobs which need artifacts from other jobs fail with a 403 Forbidden - This action cannot be performed by internal users error.

It looks like the security project bot which executes the pipeline is added as a Guest. If another user higher permissions reruns the failed job, artifacts can be downloaded.

Steps to reproduce

  • Sample policy
experiments:
  pipeline_execution_schedule_policy:
    enabled: true
pipeline_execution_schedule_policy:
- name: Test pipeline
  description: Test pipeline
  enabled: true
  content:
    include:
    - project: <security project path>
      file: <CI config>
  schedules:
  - type: daily
    start_time: '16:00'
    time_window:
      value: 600
      distribution: random
    timezone: Europe/London
  • Sample CI config
stages:
 - create_artifact
 - download_artifact

create_artifact:
  stage: create_artifact
  script: echo "This is a test" > artifact.txt
  artifacts:
    paths:
      - artifact.txt
    expire_in: 1 hour

download_artifact:
  stage: download_artifact
  dependencies:
    - create_artifact
  script: echo "This is a test"

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by 🤖 GitLab Bot 🤖