... ugh, someone to do the labour
Here is my appveyor file for WildMIDI that gathers up 32 and 64-bit releases and has appveyor host them for us:
https://github.com/Mindwerks/wildmidi/b ... pveyor.yml
Travis-CI setup depends on if someone can provide an sftp (ssh) or plain old ftp account so we can upload the results.
The new release process
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: The new release process
Sadly debug builds aren't really playable on Windows, the MSVC standard library has huge amounts of debugging and sanity checking mixed in along with not doing even the most basic optimization, and you're left with a build that usually gets surprisingly close to slideshow territory.
Before we start trying to package such artifacts we should probably see if there's a possibility of making Release builds inside the AppVeyor time limit.
Before we start trying to package such artifacts we should probably see if there's a possibility of making Release builds inside the AppVeyor time limit.
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: The new release process
Can't we take advantage of /MP or do we do that already?
Re: The new release process
I'm down to do the hard labor, just give me a few days/weeks to get my life sorted. Finally moved into my new room, but there's some finishing work and infrastructure stuff in the way of me being ready to work.
Re: The new release process
We already do /MP builds, we even do /m:2 to msbuild so that it's allowed to build two non-dependant projects simultaneous.psi29a wrote:Can't we take advantage of /MP or do we do that already?
I've submitted a PR that switches the AppVeyor builds to run a similar amount of work to my current nightly builds, just to see how long that would take.
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: The new release process
We could break the builds out a bit... build matrix of: openmw, openmw-launcher, tools
Re: The new release process
Not really, you need all parts to be able to package it, and all the pieces of OpenMW will require building the components anyway - the second longest-to-compile subproject.psi29a wrote:We could break the builds out a bit... build matrix of: openmw, openmw-launcher, tools
I should probably cut out the left over pieces of that from the ci scripts for MSVC, didn't turn out very functional in my testing.
Looking at the build times for the moment though, it seems like doing nightlies might be possible, though I'll have to look into the possibility of baking proper packages. Going to try activating LTO as well, though I don't expect that to finish inside the time limit.
- psi29a
- Posts: 5362
- Joined: 29 Sep 2011, 10:13
- Location: Belgium
- Gitlab profile: https://gitlab.com/psi29a/
- Contact:
Re: The new release process
Really? I'm able to collect the artifacts from all my builds and provide them for download over appveyor with wildmidi. (for example x32 and x64 zips).
Re: The new release process
Even when splitting the builds into multiple different parts using the build matrix, and requiring to have all their compiled objects in place for the final artifact packaging?psi29a wrote:Really? I'm able to collect the artifacts from all my builds and provide them for download over appveyor with wildmidi. (for example x32 and x64 zips).
-
- Posts: 180
- Joined: 14 Jan 2013, 03:57
Re: The new release process
I wasn't aware of this discussion, but I just did a pull request that allows travis to sync the github repo with a git repo on launchpad. You can then use launchpad to build the packages via recipes.
https://github.com/OpenMW/openmw/pull/1064
https://github.com/OpenMW/openmw/pull/1064