Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • A aml
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • argo
  • aml
  • Issues
  • #57
Closed
Open
Issue created Sep 24, 2019 by Swann Perarnau@perarnauOwner

Handling ECP mirrors

We need to figure out and document our approach to ECP mirrors and external gitlab runners.

Given the current constraints, I would recommend something using

  • gitlab environments
  • a set of protected staging/production branches
  • a separate ecp-ci pipeline that only runs on master and those other protected branches
  • a way to link external pipeline status into this gitlab instance

See this: https://docs.gitlab.com/ee/workflow/gitlab_flow.html#production-branch-with-gitlab-flow

Assignee
Assign to
Time tracking