Cygwin

Get that Linux feeling - on Windows

(experimental) Package build service

After pushing to a package git repository, an automatic build of the package is queued:

remote: scallywag: build nnnn queued

The results will appear (some time later) at https://cygwin.com/cgi-bin2/jobs.cgi (URL subject to change).

Caveats

Currently, many packages will fail to build correctly due to:

missing or insufficient BUILD_REQUIRES
missing prerequisites implied by an inherit, or other bugs
resource limits imposed by AppVeyor's free service, which is currently used to perform the actual builds

This is a prototype system, and at this stage, this is only probably useful for verifying that BUILD_REQUIRES is correct.

(Note that a successful build doesn't always mean that you have reproduced your local build: You'll also need to check the configuration step output and/or dependencies of the produced packages are the same. Consider explicitly enabling the functionality you are expecting in the options to the configure script, if it supports that (e.g. CYGCONF_ARGS, etc.), to avoid it potentially silently turning off in future, if it's requirements change.)

Controlling the build service

The following tokens are recognized in the SCALLYWAG variable set in the .cygport file:

nobuild
Disables building packages.
notest
Disables running cygport test.
deploy
For the master branch, after a successful build, the built packages are handed-off to the package uploader.

Note that currently, these packages are built using cygport all-test, and so will always be marked as test.