Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #25549
Closed (moved) (moved)
Open
Issue created Mar 20, 2018 by Isis Lovecruft@isis

Add tor CI config for AppVeyor

At the Rome meeting, it was discussed (apparently, I wasn't there that time) to have an AppVeyor config for tor. As I understand it (and please feel free to correct this ticket!), the idea is to have multiple CI systems running (which is a thing we already do!). For example, currently, we have Jenkins and we also have TravisCI for personal (Github-based) forks (as per #22636 (moved)): Jenkins tests (essentially) (Debian package-based) builds on master and known (supported) tor versions, while Travis tests anything any developer pushes (albeit only for GCC/Clang on Linux, because everything else is unsupported/slow).

We should setup an AppVeyor config for testing tor on Windows. Ideally, it should match the testing behaviour of our Jenkins/Travis builds, so that we don't get spurious errors on one system or another.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking