From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-patches@cygwin.com
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH 3/3] Cygwin: Remove .drone.yml
Date: Wed, 26 Aug 2020 22:04:09 +0100 [thread overview]
Message-ID: <20200826210409.2497-4-jon.turney@dronecode.org.uk> (raw)
In-Reply-To: <20200826210409.2497-1-jon.turney@dronecode.org.uk>
tea-ci.org was a CI service for MSYS2, but is no longer operating.
---
.drone.yml | 58 ------------------------------------------------------
1 file changed, 58 deletions(-)
delete mode 100644 .drone.yml
diff --git a/.drone.yml b/.drone.yml
deleted file mode 100644
index ad512a031..000000000
--- a/.drone.yml
+++ /dev/null
@@ -1,58 +0,0 @@
-# Build configuration for https://tea-ci.org
-# Tea CI is a fork of Drone CI with Cygwin/Msys2 support
-# Feel free to share Tea CI to more open source developers
-# https://docs.tea-ci.org/usage/overview/
-
-debug: true
-
-build:
- stage1:
- image: teaci/cygwin$$arch
- pull: true
- shell: cygwin$$arch
- commands:
- - uname -a
- - id
- - C:/cygwin-installer.exe --site http://mirrors.tea-ci.org/cygwin --local-package-dir Z:/tmp/cygwin -W -P gettext-devel,zlib-devel,libiconv,libiconv-devel,mingw64-i686-gcc-g++,mingw64-i686-zlib,mingw64-x86_64-gcc-core,mingw64-x86_64-gcc-g++,mingw64-x86_64-zlib,dejagnu,dblatex,docbook-xml45,docbook-xsl,xmlto -q &> /dev/null
- - srcdir=`pwd`
- - builddir=/oss/build-stage1
- - installdir=/oss/install-stage1
- - mkdir -p ${builddir} ${installdir}
- - cd ${builddir}
- - ${srcdir}/configure --prefix=${installdir} -v
- - make
- - make install
- - sha1sum ${installdir}/bin/cygwin1.dll /bin/cygwin1.dll
- # FIXME: Is there an easy way to package new Cygwin then install locally using setup_x86{,-64}.exe?
- - cp -vf ${installdir}/bin/cygwin1.dll /bin/cygwin1.dll
-
- test:
- image: teaci/cygwin$$arch
- pull: true
- shell: /bin/bash # Call from Linux native shell, which is a special bonus of Tea CI.
- commands:
- # In the worst case, new cygwin1.dll might fail to start with exit status 0, which fools the CI as status success.
- # The following test does not rely on cygwin exit status, instead we trust Linux grep result.
- - cygwin$$arch -c "uname -a" | grep CYGWIN_NT
- - cygwin$$arch -c "id" | grep uid
- - cygwin$$arch -c "sha1sum --tag /bin/cygwin1.dll" | grep SHA1
-
- # Compile Cygwin again using the new cygwin1.dll
- stage2:
- image: teaci/cygwin$$arch
- pull: true
- shell: cygwin$$arch
- commands:
- - srcdir=`pwd`
- - builddir=/oss/build-stage2
- - installdir=/oss/install-stage2
- - mkdir -p ${builddir} ${installdir}
- - cd ${builddir}
- - ${srcdir}/configure --prefix=${installdir} -v
- - make
- - make install
-
-matrix:
- arch:
- - 64
- - 32
--
2.28.0
next prev parent 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 [PATCH 0/3] CI update Jon Turney
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 ` Jon Turney [this message]
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-4-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).