Package building and build process

Alon Bar-Lev alonbl at redhat.com
Mon May 5 15:51:17 UTC 2014



----- Original Message -----
> From: "David Caro" <dcaroest at redhat.com>
> To: "infra" <infra at ovirt.org>
> Sent: Monday, May 5, 2014 6:39:53 PM
> Subject: Package building and build process
> 
> Hi!
> 
> Lately we had some issues when trying to build some of the projects, and we
> wanted to start a discussion to clarify what do we want and how to get there.
> 
> We can split the thread if it gets too large for all the subjects.
> 
> The main points to discuss:
> 
> * How the source tarballs should be built
>   · Should we use a jenkins job for it, so the maintainer just downloads the
>     tarball from it
>   · Should we force the maintainer to build it and supply the tarball himself
>   · Should we allow both

Not sure why you manage this discussion.
You just forgot to mention that up until now it worked perfectly ok, we had a job to build releases out of tarballs, and all worked perfectly.
It was broken when you decided not to install certain dependencies on build slaves.

Anyway...

This is up to maintainer to decide.
Build infrastructure should be able to get upstream tarball (any upstream not just ovirt) and produce binaries for all our supported platforms as a service, just like koji, brew or any downstream service.
The root resource of open source is the source tarball, this is the release not the binary.
People here at ovirt tend to confuse what open source is.

> 
> * Separate source release from binary release
> 
> * Which tools to use to build the rpms
>   · plain rpmbuild
>   · Mock
>   · Docker
>   · copr
>   · Open Build System
>   · koji

Once upstream releases source tarball, this is not important.
This is the entire idea of open *SOURCE*.

> * How to organize the rpm/tar build jobs
>   · One job for all the projects
>   · One job per-project

If we cannot provide single job for generic tarball build, we have a huge problem.

I worked very hard with all maintainers (except vdsm) to be able to achieve the standard sequence of:

# rpmbuild -tb <tarball>

Regards,
Alon Bar-Lev.

> 
> PD. Opened an etherpad to keep the points
> http://etherpad.ovirt.org/p/build_discussion
> --
> David Caro
> 
> Red Hat S.L.
> Continuous Integration Engineer - EMEA ENG Virtualization R&D
> 
> Email: dcaro at redhat.com
> Web: www.redhat.com
> RHT Global #: 82-62605
> 
> 
> _______________________________________________
> Infra mailing list
> Infra at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
> 



More information about the Infra mailing list