Opened at 2014-11-29T04:36:31Z
Closed at 2019-07-25T13:05:24Z
#2344 closed task (wontfix)
Acquire and configure a dedicated Windows build slave.
| Reported by: | daira | Owned by: | nejucomo |
|---|---|---|---|
| Priority: | normal | Milestone: | soon (release n/a) |
| Component: | dev-infrastructure | Version: | n/a |
| Keywords: | windows buildslave packaging | Cc: | |
| Launchpad Bug: |
Description
Nathan wrote at https://github.com/LeastAuthority/leastauthority.com/issues/287 :
We should see if we can get Don't Panic to setup a buildbot slave. It's in both of our interests and we can help them with setup if they provide the hardware.
Change History (3)
comment:1 Changed at 2015-01-22T16:05:17Z by daira
- Keywords packaging added
- Summary changed from collaborate with Don't Panic to set up a Windows build slave to Acquire and configure a dedicated Windows build slave.
comment:2 Changed at 2016-02-22T21:57:50Z by warner
comment:3 Changed at 2019-07-25T13:05:24Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
Buildbot has been decommissioned.
Note: See
TracTickets for help on using
tickets.
I'm testing out https://www.appveyor.com, which is free for FOSS projects. And most importantly, managed by someone else :).
I'm also adding support for running our tests under tox, since tox creates a virtualenv for you. The appveyor config should be simplified by having it run tox intead of running virtualenv/setup.py/trial directly, and then I think we can use this on all our other buildslaves too.
'tox' appears to build an sdist from your source tree, then install that into the virtualenv, then run a command of your choosing. I'm using trial allmydata.