Hello Rudolf,

On Thu, Aug 24, 2017 at 4:10 AM, Rudolf Kastl <che666@gmail.com> wrote:
Hey,

I am currently maintaining llvm trunk and mesa git snapshot repos for f25 and f26 at: https://copr.fedorainfracloud.org/coprs/che. 

One thing i would love to see is the ability to have a buildrepo and a release repo and beeing able to sync from build to release once a complete buildchain successfully built.

More thorough description of the problem and a possible solution:

* you have a dependency chain of 3 packages to build
* you need to regen repos after each package because the next package in the tree depends on the first one. (like clang on llvm)
* then after building the first 2 packages the 3rd package breaks ... you end up with a broken dep chain in the repo.

Now a workaround would be to do scratch builds first and then final repo builds. But e.g. for llvm (only the llvm library) that means... over 100 minutes buildtime using 4 builders (32bit / 64bit for 2 distro versions).

What i would love to see is to be able to build in one repository and then send (copy/rsync whatever) the built chain over to a release repository. This way also testing is possible before pushing the stuff to consumers.


So, this is interesting. This is something like auto-forking from one project to another after a successful batch build (under development). It actually could work just inside one project if the batch building would be done separately from the main project repo and only be included if successful. Ok, thanks for this input. I think we can do something about this.
 
kind regards,
Rudolf Kastl



2017-08-22 17:15 GMT+02:00 Kamil Dudka <kdudka@redhat.com>:
On Tuesday, August 22, 2017 5:03:06 PM CEST Michal Novotny wrote:
> On Tue, Aug 22, 2017 at 4:40 PM, Kamil Dudka <kdudka@redhat.com> wrote:
> > On Tuesday, August 22, 2017 1:51:44 PM CEST Michal Novotny wrote:
> > > Hey Kamil,
> > >
> > > On Tue, Aug 22, 2017 at 12:07 PM, Kamil Dudka <kdudka@redhat.com> wrote:
> > > > On Tuesday, August 22, 2017 9:04:24 AM CEST Matthias Runge wrote:
> > > > > - the ability to directly upload srpms; that is, one can store spec
> > > > >
> > > > >   files etc. on the local machine. I'm undecided, if integrating a
> > > > >   distgit on copr would solve any issues or would introduce more,
> >
> > like
> >
> > > > >   diverging specs.
> > > >
> > > > Building packages from dist-git is already possible via 'copr
> > > > buildfedpkg'.
> > > > The problem is that the last time I tried, it only worked for the
> >
> > official
> >
> > > > Fedora branches.  All attempts to build something from a
> >
> > private-kdudka-*
> >
> > > > branch failed with the well known "Could not find the dist from branch
> > > > name"
> > > > failure of fedpkg.  Unless arbitrary dist-git branches are suported,
> >
> > the
> >
> > > > 'copr buildfedpkg' command is pretty useless.
> > >
> > > Actually, we already support arbitrary dist-git branches in COPR
> >
> > Sounds good.  I wanted to check this:
> >
> > % copr buildfedpkg --branch private-kdudka-libcurl-nss --clone-url
> > https://src.fedoraproject.org/rpms/curl.git kdudka/tmp
> >
> > Build was added to tmp:
> >   https://copr.fedorainfracloud.org/coprs/build/592748/
> >
> > Created builds: 592748
> > Watching build(s): (this may be safely interrupted)
> >
> >   16:20:56 Build 592748: importing
> >
> > But the task hangs indefinitely in the "importing" state.  You can see
> > that
> > http://copr-dist-git.fedorainfracloud.org/per-task-logs/592748.log still
> > grows with obvious periodicity.
> >
> > Am I doing anything wrong?
>
> Uh, not really. fedpkg was not installed on the production machine thus the
> import was failing.
> Note that this is still slightly under development but it should definitely
> work as a feature in
> any case.

OK.  Thank you for working on it!  I am looking forward to use it one day...

> > Kamil
> >
> > > and we also aim
> > > to be able to build from any dist-git (at least being based on
> > > https://src.fedoraproject.org/rpms/dist-git).
> > >
> > > Currently we also support building from copr-dist-git in addition to
> >
> > Fedora
> >
> > > DistGit but
> > > we need to reflect that in our API and in copr-cli interface by renaming
> > > the subcommand.
> > > (or providing the new generic one while keeping the old one for some
> >
> > time)
> >
> > > Then there is actually also the new rpkg client (based on pyrpkg lib):
> > > https://src.fedoraproject.org/rpms/rpkg-client
> > > that you can use for launching COPR builds from any dist-git repo being
> > > locally checked out.
> > >
> > > > Kamil
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org