Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #238464
Closed
Open
Issue created Aug 18, 2020 by Nick Nguyen@nhxnguyenDeveloper

Geo: Replicate Pipeline Artifacts

Summary

A new data type, Ci::PipelineArtifact was introduced in GitLab 13.3.

It would be useful for this to be replicated to a secondary (#235918 (comment 395623970)).

Proposal

Enlist help from grouptesting to implement replication for PipelineArtifact using the self-service framework with assistance from Geo. This is what the SSF was intended for and presents another opportunity to receive feedback on and improve the SSF.

Edited Aug 20, 2020 by Nick Nguyen
Assignee
Assign to
Time tracking