Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • 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
  • James Willenbring
  • Trilinos
  • Issues
  • #1156

Closed
Open
Created Mar 20, 2017 by James Willenbring@jmwilleMaintainer

Site name consistency

Created by: jwillenbring

@trilinos/framework @bartlettroscoe @bmpersc

Kitware is implementing a feature that will help us identify when a test goes missing on the dashboard. To do this, a consistent site name is required. Our machines are currently identified on the CDash dashboard by machine name. However, in situations where jobs float (including parameterized builds on the other build farm), jobs can run on different machines, and are currently listed as different sites. Could we perhaps assign a single site to all machines on the build farm, or define a "site" per job run?

Done for this ticket is to better define the issue, determine how to get site consistency, and implement the solution.

Assignee
Assign to
Time tracking