Opened at 2020-09-11T10:03:05Z
Closed at 2020-09-15T11:18:46Z
#3406 closed task (fixed)
Upgrade CircleCI config to version 2.1
| Reported by: | chadwhitacre | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Support Python 3 |
| Component: | dev-infrastructure | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
In #3405 we want to add Python 3.6 on Windows to CI. We have two CI services, CircleCI and GitHub Actions. We use the former for exercising the test suite, so it seems that we should try to continue using it for the same on Windows. The easiest (only?) way to use Windows on CircleCI is via features—orbs and executors—that are only available with version 2.1 of their configuration format. However, there are some other changes with v2.1 that we'll have to take on board first, not least of which is an approach to config reusability that imposes new restrictions on job names: no more dots!
Change History (2)
comment:1 Changed at 2020-09-14T12:21:53Z by exarkun
comment:2 Changed at 2020-09-15T11:18:46Z by chadwhitacre
- Resolution set to fixed
- Status changed from new to closed
Done in https://github.com/tahoe-lafs/tahoe-lafs/pull/809, though following on from exarkun's comment the plan is to implement Python 3 + Windows under GHA.
The ticket description doesn't describe the current situation quite correctly. We currently use GitHub? Actions to run both test suites on both Windows and macOS: