[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zlib-devel
Subject:    [Zlib-devel] Organizing zlib CI
From:       cblume () google ! com (Chris Blume)
Date:       2019-11-12 1:18:38
Message-ID: CAPHsw360JW--EacydvtT4uYqikxKAHjQP+EYkoXxycU=5zQ4oA () mail ! gmail ! com
[Download RAW message or body]

Backstory:
A few of us would like to add continuous integration (CI) to zlib. AppVeyor
seems to be our best bet at the moment. Eventually, we would like to
support more platforms such as Power and ARM. For that, we'll need a more
complicated infrastructure that we manage ourselves as part of zlib.
Starting with AppVeyor will help get the CI ball rolling.

Daniel Black had a great suggestion that we use CMake to create the Visual
Studio Solution that AppVeyor needs. I can then connect that VS Solution
and zlib's existing unit tests to AppVeyor's expected test result format.

Daniel, does that work for you?

Chris Blume | Software Engineer | cblume at google.com | +1-614-929-9221
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://madler.net/pipermail/zlib-devel_madler.net/attachments/20191111/2bc20fbb/attachment.html>

[prev in list] [next in list] [prev in thread] [next in thread]