Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D dynamorio
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,467
    • Issues 1,467
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 44
    • Merge requests 44
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • 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
  • DynamoRIO
  • dynamorio
  • Issues
  • #4131
Closed
Open
Issue created Feb 24, 2020 by Derek Bruening@derekbrueningContributor

Investigate Appveyor alternatives for more parallel builds: Github Actions; Travis; CircleCI

Appveyor's big downside is the single sequential job serialized across both dynamorio and drmemory repositories and across PR's and master merges. One single job is now down to ~23-24 mins thanks to #4059 (closed) which is not that different from a Travis invocation, but the lack of parallelism does cause pain.

Possible alternatives that now include Windows (all quite recently):

  • Github Actions
  • Travis: looks like it has only VS2017 and very few packages and is in early stages
  • CircleCI
Assignee
Assign to
Time tracking