Add .cirrus.yml config for Cirrus-CI continuous integration #15

2019-06-09T03:06:54-05:00

emaste commented

2019-06-09 03:06:54 -05:00

(Migrated from github.com)

Starting with Alpine and FreeBSD 11 and 12 tasks, others to be added.

Result from my fork: https://cirrus-ci.com/build/5686867601653760

Starting with Alpine and FreeBSD 11 and 12 tasks, others to be added. Result from my fork: https://cirrus-ci.com/build/5686867601653760

z3ntu commented

2019-06-09 04:56:46 -05:00

(Migrated from github.com)

See also #6

Youw commented

2019-06-09 20:35:06 -05:00

(Migrated from github.com)

Even with #6, this does looks like an improvement. @z3ntu or do you suggest to merge the effort, or smth?

Also, in order to actually have this working, someone from libusb organisation has to give access to Cirrus-CI to this repository.

Even with #6, this does looks like an improvement. @z3ntu or do you suggest to merge the effort, or smth? Also, in order to actually have this working, someone from libusb organisation has to give access to Cirrus-CI to this repository.

z3ntu commented

2019-06-10 05:18:31 -05:00

(Migrated from github.com)

I'd rather use the builds.sr.ht service as it's open-source and could theoretically be self-hosted (and I doubt cirrus ci is open-source).

Qbicz commented

2019-07-23 13:31:23 -05:00

(Migrated from github.com)

Since we already have Alpine and FreeBSD covered, I would suggest to close this PR.

@z3ntu do you see value in having Cirrus configuration available? Or in testing multiple versions of FreeBSD as @emaste did?

Since we already have Alpine and FreeBSD covered, I would suggest to close this PR. @z3ntu do you see value in having Cirrus configuration available? Or in testing multiple versions of FreeBSD as @emaste did?

z3ntu commented

2019-07-23 14:29:39 -05:00

(Migrated from github.com)

builds.sr.ht also has support for FreeBSD 11.x and FreeBSD CURRENT if we want that. Our freebsd builds use freebsd/latest which is FreeBSD 12 currently. So if you want that, I can add them.

But I think we're good with the current set of CIs (Alpine Linux with musl libc; Arch Linux with glibc, FreeBSD and three variants of Windows (mingw, cygwin & msbuild))

What could be done is to create "release candidate" CI configuration that makes a build for each OS supported on builds.sr.ht (Alpine Linux, Arch Linux, Debian, Fedora, FreeBSD, NixOS, OpenBSD, Ubuntu) and all versions supported there if someone has too much free time on their hands^^

builds.sr.ht also has support for FreeBSD 11.x and FreeBSD CURRENT if we want that. Our freebsd builds use `freebsd/latest` which is FreeBSD 12 currently. So if you want that, I can add them. But I think we're good with the current set of CIs (Alpine Linux with musl libc; Arch Linux with glibc, FreeBSD and three variants of Windows (mingw, cygwin & msbuild)) What could be done is to create "release candidate" CI configuration that makes a build for each OS supported on builds.sr.ht (Alpine Linux, Arch Linux, Debian, Fedora, FreeBSD, NixOS, OpenBSD, Ubuntu) and all versions supported there if someone has too much free time on their hands^^

emaste commented

2019-07-23 14:49:42 -05:00

(Migrated from github.com)

builds.sr.ht sounds like a good approach, although IMO there's not much downside of having a configuration for Cirrus-CI in the tree also, as with .travis.yml / .appveyor.yml; people doing development on their fork may find it convenient.

Qbicz commented

2019-09-28 10:23:32 -05:00

(Migrated from github.com)

@youw, @z3ntu, I support merging this if you agree. We don't have to have Cirrus set up for this repo, this could be for contributors convenience.

Youw (Migrated from github.com) approved these changes

2019-09-28 12:27:01 -05:00

Youw (Migrated from github.com) left a comment

sounds fare

z3ntu (Migrated from github.com) reviewed

2019-09-28 14:05:05 -05:00

.cirrus.yml

					
				@ -0,0 +4,4 @@

				        install_script: apk add autoconf automake g++ gcc libusb-dev libtool linux-headers eudev-dev make musl-dev

				        script:

				                - ./bootstrap

				                - ./configure || { cat config.log; exit 1; }

Why does this configure statement have the statement behind but not the others?

emaste (Migrated from github.com) reviewed

2019-11-29 08:51:06 -06:00

.cirrus.yml

					
				@ -0,0 +4,4 @@

				        install_script: apk add autoconf automake g++ gcc libusb-dev libtool linux-headers eudev-dev make musl-dev

				        script:

				                - ./bootstrap

				                - ./configure || { cat config.log; exit 1; }

Oh, I probably added that while trying to track down some problem building on alpine, and did not run into a problem on the other OSes that required more details. It's probably a good idea for all cases and I'll update the PR.

emaste commented

2019-11-29 09:57:58 -06:00

(Migrated from github.com)

Here's an Alpine, FreeBSD 11, FreeBSD 12 build: https://cirrus-ci.com/build/4977906178064384

Youw commented

2020-01-22 06:08:37 -06:00

(Migrated from github.com)

One last note before merge: can we move this file to a .builds subfolder?

One last note before merge: can we move this file to a `.builds` subfolder?

emaste commented

2020-01-22 07:15:13 -06:00

(Migrated from github.com)

One last note before merge: can we move this file to a .builds subfolder?

No, Cirrus-CI only looks at the root dir of the repository (as does Travis-CI etc.)

> One last note before merge: can we move this file to a `.builds` subfolder? No, Cirrus-CI only looks at the root dir of the repository (as does Travis-CI etc.)

Youw commented

2020-01-22 08:00:39 -06:00

(Migrated from github.com)