Re: Merge pgjdbc-parent-poms project into pgjdbc please
От | Vladimir Sitnikov |
---|---|
Тема | Re: Merge pgjdbc-parent-poms project into pgjdbc please |
Дата | |
Msg-id | CAB=Je-FuSSuMmX_OvCHzb_rPS=3TOu2eDZ+5H953abPEE_phUQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Merge pgjdbc-parent-poms project into pgjdbc please (Álvaro Hernández Tortosa <aht@8kdata.com>) |
Ответы |
Re: Merge pgjdbc-parent-poms project into pgjdbc please
Re: Merge pgjdbc-parent-poms project into pgjdbc please |
Список | pgsql-jdbc |
Pavel, would you post another build log as you add parent-poms build/package? 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. The *.spec file in question might live in the main pgjdbc repository, or in a side one. There seem to be a copr-cli client interface, thus we might be able to trigger a copr build from within Travis job. 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? Vladimir
В списке pgsql-jdbc по дате отправления: