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
  • #1157

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

Set up Windows VMs for Trilinos testing

Created by: jwillenbring

@trilinos/framework

As discussed earlier today, we need to set up a couple of VMs for Trilinos testing on Windows. Here is a rough outline of the associated tasks:

  1. Install all necessary software on 1st VM. Visual Studio 2015 is the current target at a high level, but we also need git (and possibly putty to support git), CMake, blas, lapack and mpi.
  2. Test first VM by building some subset of Trilinos.
  3. When VM seems to be in good shape, copy the VM so that we eventually have 1 that runs Jenkins jobs, and 1 developers are allowed to log directly in to for debugging.

We can split some of this into separate tickets in the future if it makes sense.

Assignee
Assign to
Time tracking