Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,730
    • Issues 1,730
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 59
    • Merge Requests 59
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ParaView
  • ParaViewParaView
  • Issues
  • #20414

Closed
Open
Opened Jan 04, 2021 by Utkarsh Ayachit@utkarsh.ayachit⛰Owner0 of 3 tasks completed0/3 tasks

Gitlab-CI master bug

I am creating this issue to discuss and track missing features / bug with gitlab ci.

  • get Do: test working. Without this, it's not easy for developers to tell which builds must be run on the MR. For example, we have spack and doc builders that don't need to be run on MRs.
  • Make it easier to go to CDash link. Once Do: test starts working, this will probably work out of the box. The way it is exposed currently is confusing.
  • ParaView-Superbuild CI jobs don't show up correctly on CDash. The builds and tests are not getting appended.

cc: @ben.boeckel @cory.quammen @mwestphal @vbolea

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#20414