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 36,993
    • Issues 36,993
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,435
    • Merge requests 1,435
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #196829

Closed
Open
Created Jan 15, 2020 by Rachel Nienaber@rnienaberDeveloper

Providing Guidance on Isolation issues

As discussed in the Isolation Working Group, we would like to create guidance that engineers can follow when isolation issues are identified.

When the Infrastructure Team (or another team), identifies an isolation issue, they will contact the group responsible, and the thought it that it would be good to be able to provide that group with guidance on how they could potentially address the problem.

The outcome of this issue should be a set of guidance added to developer documentation or the handbook.

/cc @clefelhocz1

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking