On Wednesday, August 23, 2017 1:46:46 PM CEST Miroslav Suchý wrote: > Do you use Copr for building packages for nightlies? For building packages > before pull request is merged? Yes, not particulary me -- but I helped to guys in pgjdbc project to setup CI: https://copr.fedorainfracloud.org/coprs/g/pgjdbc/pgjdbc-travis/ https://github.com/pgjdbc/pgjdbc/blob/master/packaging/rpm/fedora-image/copr-ci-git > Do you have your set up described somewhere? No, since it is too complicated. Tito is a burden for distro-agnostic upstream. Since upstream had travis-ci already enabled, my plan was to generate src.rpm in travis-ci and submit build into copr (together with other CI tasks). Two major problems: 1. Travis is (or was that time) debian/ubuntu only, so it is actually not very convenient to install all the necessary tooling there; so the work-around was to use Fedora docker-image and that image is pulled in for each CI run. 2. You need to store your copr credentials into git. You can cipher that, but at least it is not convenient to store *your own* copr authentication token into git repo, because always at least other git committers can decipher it. You also need to re-generate your API token twice a year (it means you need to bother the upstream with "useless" commits, but the worst thing is that you need to regularly go back and pay attention to fixing the CI). Being able to specify (a) scm repo, (b) build deps and (c) any (turing complete) script within the git repo (to generate the sources) would make setting up the CI a trivial task. Pavel > What is the name of your > project? > > Please let me know. Either here or via private reply. > It will help me to understand your use of Copr and to make Copr better. > > Thanks in advance. > > Miroslav Suchy > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
