public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH 0/3] CI update
Date: Wed, 26 Aug 2020 22:04:06 +0100	[thread overview]
Message-ID: <20200826210409.2497-1-jon.turney@dronecode.org.uk> (raw)

Since we recently had the unpleasant surprise of discovering that Cygwin
doesn't build on F32 when trying to make a release, this adds some CI to
test that.

Open issues: Since there don't seem to be RedHat packages for cocom, this
grabs a cocom package from some random 3rd party I found on the internet.
That might not be the best idea :).

This also updates other CI configurations.

Jon Turney (3):
  Cygwin: Add .appveyor.yml
  Cygwin: Add github action to cross-build on Fedora
  Cygwin: Remove .drone.yml

 .appveyor.yml                | 69 ++++++++++++++++++++++++++++++++++++
 .drone.yml                   | 58 ------------------------------
 .github/workflows/cygwin.yml | 45 +++++++++++++++++++++++
 3 files changed, 114 insertions(+), 58 deletions(-)
 create mode 100644 .appveyor.yml
 delete mode 100644 .drone.yml
 create mode 100644 .github/workflows/cygwin.yml

-- 
2.28.0


             reply	other threads:[~2020-08-26 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 21:04 Jon Turney [this message]
2020-08-26 21:04 ` [PATCH 1/3] Cygwin: Add .appveyor.yml Jon Turney
2020-08-26 21:04 ` [PATCH 2/3] Cygwin: Add github action to cross-build on Fedora Jon Turney
2020-08-26 21:04 ` [PATCH 3/3] Cygwin: Remove .drone.yml Jon Turney
2020-08-27  8:49 ` [PATCH 0/3] CI update Corinna Vinschen
2020-08-27 19:29   ` Brian Inglis
2020-08-28  8:43     ` Corinna Vinschen
2020-08-28 13:57       ` Brian Inglis
2020-08-28 13:24 ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200826210409.2497-1-jon.turney@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-patches@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).