Opened at 2020-01-20T18:47:38Z

Closed at 2020-04-13T14:05:53Z

#3277 closed defect (fixed)

Move Windows CI to GitHub Actions

Reported by: exarkun Owned by: exarkun
Priority: normal Milestone: undecided
Component: unknown Version: n/a
Keywords: Cc:
Launchpad Bug:

Description

GitHub? offers free hosted CI supporting several platforms including Windows ("Windows Server 2019").

Tahoe-LAFS currently uses Appveyor. Appveyor is a great free (and paid) Windows CI service. However, Appveyor is kind of slow and has a weird configuration system. Additionally, Appveyor refuses to update GitHub? with build results. Thus, when Windows support breaks, from GitHub? it still looks like everything is working. This goes a long way towards defeating the purpose of CI.

Thus, replace Appveyor with GitHub? actions for Windows CI so that we actually have Windows CI information visible on GitHub? PRs.

Change History (3)

comment:1 Changed at 2020-01-20T18:48:02Z by exarkun

  • Owner set to exarkun
  • Status changed from new to assigned

comment:2 Changed at 2020-01-20T18:48:36Z by exarkun

GitHub? Actions documentation is very ... fresh.

Examples can be instructive. Here is one such: ​https://github.com/Julian/jsonschema/tree/master/.github/workflows

comment:3 Changed at 2020-04-13T14:05:53Z by Sajith Sasidharan <sajith@…>

  • Resolution set to fixed
  • Status changed from assigned to closed

In 5862e1b/trunk:

Use GitHub? Actions for CI.

Fixes: ticket:3277

Note: See TracTickets for help on using tickets.