search

Juniper / libxo

The libxo library allows an application to generate text, XML, JSON, and HTML output using a common set of function calls. The application decides at run time which output style should be produced.
http://juniper.github.io/libxo/libxo-manual.html
BSD 2-Clause "Simplified" License
321 stars 48 forks source link

Add FreeBSD to TravisCI config #72

Closed jbeich closed 1 year ago

jbeich commented 4 years ago

TravisCI supports FreeBSD nowadays. Let's see how well it works.

This is an alterantive to #66 in case you don't want to sign up the repo with CirrusCI or maintain two CI configs.

philshafer commented 3 years ago

I use the “script” line to give me information about the build so I can more easily reproduce issues. Can you change be done in a way that retains this?

Thanks, Phil

On Nov 24, 2020, at 1:01 PM, Jan Beich notifications@github.com wrote:

@jbeich commented on this pull request.

In .travis.yml https://github.com/Juniper/libxo/pull/72#discussion_r529773930:

@@ -1,6 +1,19 @@ language: c

-script: printenv && uname -a && ls -l && /bin/sh -x ./bin/setup.sh && cd build && ../configure --enable-warnings && make && sudo make install && make test +os: +- linux +- freebsd + +before_install:

jbeich commented 3 years ago

Like this? I can't test on TravisCI anymore due to usage limits but see https://travis-ci.org/github/Juniper/libxo/builds/746617293

philshafer commented 3 years ago

“../configure" fails, but we can’t see the “config.log” output file. Can we get a copy of that?

Thanks, Phil

On Nov 29, 2020, at 2:53 PM, Jan Beich notifications@github.com wrote:

Like this? I can't test on TravisCI anymore due to usage limits but see https://travis-ci.org/github/Juniper/libxo/builds/746616668 https://travis-ci.org/github/Juniper/libxo/builds/746616668 — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Juniper/libxo/pull/72#issuecomment-735445042, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAROIOE7PZIGO3JCEOVXHBDSSKRELANCNFSM4NHEK7PQ.

jbeich commented 3 years ago

If you'd like to switch to GitHub Actions in future, see https://github.com/actions/runner/issues/385#issuecomment-702592563

jbeich commented 3 years ago

“../configure" fails, but we can’t see the “config.log” output file.

It doesn't fail anymore. I've updated the above comment to point to a more recent build. No clue why CI status doesn't propagate to this PR: maybe you need to re-install TravisCI from marketplace.

See also https://travis-ci.community/t/github-status-not-posted-on-commits-on-repositories-using-legacy-service-integration/7798