summaryrefslogtreecommitdiffstats
path: root/appveyor.yml
Commit message (Collapse)AuthorAgeFilesLines
* appveyor: Set git core.autocrlf setting to true.Jose Fonseca2018-08-211-0/+7
| | | | | | | | | | | | | | | | The git core.autocrlf setting defaults to true (ie, all text files get checked out as CRLF on Windows), except on Appveyor where's set to "input" (ie, all text files get checked out with the upstream repository's line endings, which for us typically means LF.) And this was masking on Appveyor a regression in gen_xmlpool.py processing t_options.h with CRLF line endings. This change makes core.autocrlf to be true, which would have enabled to immediately catch the issue, as seen in https://ci.appveyor.com/project/jrfonseca/mesa/build/51 Reviewed-by: Roland Scheidegger <[email protected]>
* appveyor: Consume LLVM 5.0.1.Jose Fonseca2018-06-161-2/+2
| | | | | | https://ci.appveyor.com/project/jrfonseca/mesa/build/47 Reviewed-by: Roland Scheidegger <[email protected]>
* appveyor: Build with MSVC 2015.Jose Fonseca2018-02-221-5/+5
| | | | | | | | | | | | | | | The MSVC version we (at VMware) primarily care about from now on is 2015. See https://ci.appveyor.com/project/jrfonseca/mesa/build/46 We can drop support for building with 2013 in a future commit. I'm not aware of significant changes in C99/C11 support from MSVC 2013 to 2015, but there's no point in continuing supporting old MSVC versions when nobody cares. Reviewed-by: Brian Paul <[email protected]> Reviewed-by: Roland Scheidegger <[email protected]>
* appveyor: Update dependencies.Jose Fonseca2017-03-291-4/+6
| | | | | | | - Use explicit versions everywhere. - Avoid deprecate `--egg` pip option. Reviewed-by: Roland Scheidegger <[email protected]>
* appveyor: Update winflexbison download URL.Jose Fonseca2016-09-131-1/+1
| | | | This particular version got moved into a `old_versions` subdirectory.
* appveyor: Force Visual Studio 2013 image.Jose Fonseca2016-08-111-0/+2
| | | | | It seems the default build image is now Visual Studio 2015, and Visual Studio 2013 is not installed.
* appveyor: Install pywin32 extensions.Jose Fonseca2016-08-111-0/+2
| | | | | AppVeyor build images seem to have been upgraded to Python 2.7.12, but no longer have pywin32 pre-installed.
* appveyor: Run unit tests.Jose Fonseca2016-04-141-0/+3
| | | | Reviewed-by: Roland Scheidegger <[email protected]>
* appveyor: Bump shallow clone depth.Jose Fonseca2016-02-031-2/+9
| | | | | | | | | | | | | To prevent build failures when a large patch series is committed, like happened in https://ci.appveyor.com/project/jrfonseca-fdo/mesa/build/322 due to 10 commits between dac2964f3ebd96d5ac227984ab0cd79c2c3b2a1a and 6f428328d34bed16edb8709e4a117eb710d7893d where submitted before the build slave started the git clone. 100 commits should be bigger than any patch series seen in practice, and it takes practically the same time to download as 5 commits. Reviewed-by: Roland Scheidegger <[email protected]>
* appveyor: Cache winflexbison archive.Jose Fonseca2015-12-081-3/+7
| | | | | | | | | | | | | Unforunately the Appveyor -> SourceForge connection seems a bit unreliable, causing frequent build failures while downloading winflexbison (approx once every 2 days). Fetching winflexbison archive into Appveyor's cache should eliminate these. Fetching Python modules from PyPI doesn't seem to be a problem, so they are left alone for now, though they could eventually get the same treatment.
* appveyor: Initial integration.Jose Fonseca2015-12-021-0/+62
AppVeyor doesn't require an appveyor.yml in the repos (in fact it has some limitations as noted in comments below), but doing so has two great advantages over the web UI: - appveyor.yml can be revisioned together with the code, so instructions should always be in synch with the code - appveyor.yml can be reused for people's private repositories (be on fdo or GitHub, etc.) Acked-by: Roland Scheidegger <[email protected]>
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-15 14:27:49 +0000