From: john at keeping.me.uk (John Keeping)
Subject: Gerrit features and Docker based testing
Date: Sat, 21 Oct 2017 14:05:39 +0100 [thread overview]
Message-ID: <20171021130539.GB2393@john.keeping.me.uk> (raw)
In-Reply-To: <d839460c2eedd5f309184b3292304d76@codeaurora.org>
On Thu, Oct 19, 2017 at 05:07:30PM -0600, bbuhlig at codeaurora.org wrote:
> Hi, Cgit is frequently paired with Gerrit installations, so I have a
> some Gerrit integration features I'd like to contribute. One is a Lua
> authentication filter for Gerrit. Background is that Gerrit allows
> different
> users to have access to different repos, so in essence this auth filter
> leverages the user's Gerrit login HTTP cookie to access the Gerrit REST
> API,
> which it uses to figure out whether the logged in user should have
> access to
> the particular repo.
>
> Anyway, to help ensure it keeps working along with the Lua code itself,
> I'd
> ideally like to contribute some tests for it. But the environment those
> tests would need to run in would be a bit complicated, in particular
> needing:
>
> (1) the auth filter's Lua package dependencies installed-
> - specifically: crypto, ssl.https and ltn12
> and,
> (2) a test Gerrit instance configured that the filter could talk to,
> - or a simple python/node.js based webserver that looks
> sufficiently
> like the part of the Gerrit REST API that the filter cares
> about
>
> An obvious way to define this environment would be a Dockerfile that the
> "make test" command invokes Docker against. To enable people who don't
> care
> about the Gerrit auth-filter, the makefile could be setup to skip the
> test
> if Docker isn't installed on the build machine. But unless the cgit
> maintainers were to trigger the tests in a build environment with Docker
> available, the auth filter code would eventually get stale and break.
>
> Assuming the above sounds reasonable and I provided said feature and
> tests,
> would it be possible for the cgit maintainers to generally have Docker
> available when regularly running "make test"?
I wouldn't want the top-level "make test" to add additional
dependencies, but I'm not sure that's necessary here.
Assuming this lives under contrib/, it can have its own build and test
infrastructure that is separate from the main CGit source.
prev parent reply other threads:[~2017-10-21 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 23:07 bbuhlig
2017-10-21 13:05 ` john [this message]
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=20171021130539.GB2393@john.keeping.me.uk \
--to=cgit@lists.zx2c4.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 NNTP newsgroup(s).