Hi Saúl,
> Currently the testing facility is provided by and ran by our nice
> friends running iojs. They have enough on the their shoulders, and since
> libuv binaries are not a requirement for iojs (it uses it bundled) I'd
> rather see if we can achieve this with appveyor.
Ah, I understand. That's a lot clearer.
> Running tests there is fine, as long as it doesn't add much noise. I'd
> like to explore how the release making process would work, but I haven't
> gotten around to do it yet :-(
The appveyor config doesn't do any tests, it just builds the binaries
and creates an installer. If the status of the build changes (success
<-> fail) then an email notification is sent to the github repo owner,
but that can be disabled.
For every each push that ends up in github.com/libuv/libuv (or
wherever) the build is triggered. I haven't found a way of it not
doing that. If the push includes a git tag, the tag name is used as
the installer version number and it is deployed to github, otherwise
it uses "1.5.0.{build}" as the version number and doesn't deploy to
github, but does save it.
It might be better to have the appveyor version number for non-tag
pushes set to something that wasn't related to a release so there was
less of a maintenance burden. "testing-{build}" or something perhaps.
Assuming the file structure doesn't change that should be it.
> There are a few Windows issues / PRs which I'd like to address for next
> libuv release, I'll see if I can have a look at this as well.
That would be great, it would make my life lots easier.
Cheers,
Roger
--
You received this message because you are subscribed to the Google Groups
"libuv" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/libuv.
For more options, visit https://groups.google.com/d/optout.
