Re: Merge pgjdbc-parent-poms project into pgjdbc please

On Sunday 24 of January 2016 23:55:22 Vladimir Sitnikov wrote:
> Pavel, would you post another build log as you add parent-poms
> build/package?

I'll send you soon the build logs, I do not plan to add parent-poms as
separate fedora package (separate spec file) -- it does not make sense,
the package would be used just by jdbc plugin during build (and additional
bureaucracy would be worthless).  I'll rather make the package build-able
in 2 phases.

> I've poked around copr.fedorainfracloud.org a bit, and it looks like
> it can fetch "rpm build script" from git and copr can be triggered via
> webhook.
> This means we can setup GitHub to trigger a copr build on new commits.

Right, that is the "CI" I talked about.

> The *.spec file in question might live in the main pgjdbc repository,
> or in a side one.

Wow, having this in upstream repo would be perfect.

> There seem to be a copr-cli client interface, thus we might be able to
> trigger a copr build from within Travis job.

Right, that is possible too, but I'm not sure how to create "pseudo-user";
copr-cli is usually run by real user's credentials -- so if you don't mind
it is OK.  I'll check; but the webhook would be better.

> What I do not like is "project" in copr seems to bind to a specific person.
> Is there a way to create copr account for pgjdbc community, so the
> copr job can be managed by multiple developers?

For this you need to have new Fedora group.  I'll try to request one
called like @pgjdbc -- but to allow you to access that group in Copr,
you'll need to have fedora account (FAS).

Pavel