From: Anthony Green <green@moxielogic.com>
To: libffi-discuss <libffi-discuss@sourceware.org>
Subject: libffi PR builds on travis-ci
Date: Mon, 9 Mar 2020 15:11:20 -0400 [thread overview]
Message-ID: <CACxje5-AiK=JTuzjzhJfS0MCMup5TyB1+UkB0Y4=UwGTQHWinA@mail.gmail.com> (raw)
libffi pull request builds on travis-ci have been failing for a while, but
now they are fixed.
At issue was the use of a travis-ci secret environment variable used as API
keys for https://rl.gl. As it happens, travis-ci doesn't allow the use of
these secret values in pull request builds -- only in the master and
feature branch builds. And so I implemented something called "policy bound
API keys" in rlgl. A policy bound API key is a key that can only be used
with a specific policy. So, in this case, I've bound
0LIBFFI-0LIBFFI-0LIBFFI-0LIBFFI to https://github.com/libffi/rlgl-policy.git.
This API key can be shared publicly, so now it is hard-coded in the
travis-ci build/test scripts, and used for every build.
The bottom line is that PR travis-ci tests are working again!
AG
reply other threads:[~2020-03-09 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CACxje5-AiK=JTuzjzhJfS0MCMup5TyB1+UkB0Y4=UwGTQHWinA@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
/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).