5 May
2014
5 May
'14
6:19 p.m.
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Wo19qiqIGVxkOaVEgPPs7nOPlwUAGeqca
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
I'll add some pros and cons I see for each point, and others someone (I c=
an't
see who, please qritw your nick there) wrote in the pad:
On Mon 05 May 2014 05:39:53 PM CEST, David Caro wrote:
> * How the source tarballs should be built
> =C2=B7 Should we use a jenkins job for it, so the maintainer just dow=
nloads the
> tarball from it
+ reproducible
+ automatizable
- extra jenkins job load
> =C2=B7 Should we force the maintainer to build it and supply the tarb=
all himself
+ The maintainer has full control on how it's generated
- Might introduce human errors
- extra maintainer work
- non-automatizable
- makes it hard to do nightlies (from the pad)
> =C2=B7 Should we allow both
same pluses as before
- extra work for everyone
- plus for confusion on how to do it for the maintainers
> * Separate source release from binary release
+ Logical separation from source and binary, as the source is our prima=
ry
deliverable
- To test the code you already need the binaries, no point on duplicati=
ng the
release effort
This is meant to separate our main deliverable (source code) from seconda=
ry one
(the binaries).
>
> * Which tools to use to build the rpms
> =C2=B7 plain rpmbuild
+ simple build process
- hard setup/cleanup as it needs to install dependencies from diffe=
rent
sources and then clean them up
- needs the slave to be blocked as it needs to install/remove
dependencies from different repos
- only rpm
> =C2=B7 Mock
+ stable
+ each build is independent from the system
+ same build system as koji
- uses quite a lot of space
- it's not straight-forward to use
- only rpm
> =C2=B7 Docker
+ Very simple to use
+ moderate disk usage
+ each build is independent from the system
+ not only rpm
+ it's getting a lot of focus (from RedHat and a lot
of others)
- not so stable
> =C2=B7 copr
+/- external service
+ simple to use (simple api/ui)
- only rpm
- quite new
> =C2=B7 Open Build System
+/- external service
+ not only rpm
- complex api/ui
> =C2=B7 koji
+/- external service
+ official fedora build system
- only rpm
- there were some issues that prevented us from already building th=
ere,
anyone knows more details?
>
>
> * How to organize the rpm/tar build jobs
> =C2=B7 One job for all the projects
+ less confusion when building, one place for everything
- really hard to select a specific project artifacts
- really hard to automate
- really hard to filter per-project builds
> =C2=B7 One job per-project
+ easy to filter per-project and see project status
+ easy to automate processes to get artifacts from it
+ easy to customize per-project dependencies
- might create confusion on where to build your tarball
>
>
>
> PD. Opened an etherpad to keep the points
> http://etherpad.ovirt.org/p/build_discussion
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro@redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--Wo19qiqIGVxkOaVEgPPs7nOPlwUAGeqca
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJTZ7oUAAoJEEBxx+HSYmnDI4AH/136ZcnkHittSPu1XvHRZcMs
X0fwFFhCRpMyaHaNzNog7CPP2fh88oOqkXTs2Ha8L2V8+Sx5Gdc2kvDbnmVKKDfo
AFEOkPfvzJHTQ7mViz7yGufW3FWVZqutYIDNe734yvuv5ZEQt0fI7LPGK5hIBejZ
Hnd7pL9NAqdKtU5Pj6htTVGZKfg91TQYSqvqGwW7pFrxV69UjtfP8XCIIM3vyQR2
43ekJ6s8W5Tvsa0ZZNSDa5vKiMiCP8XmDMlM/82t+eA1gbWT9EpZouJoaTg7bp2z
gDvjE/ekgzZOo+YW/EJfiRtzLTYX3PTHzCnSHfoxogDG57GoYlRbjzo2WPAMWXE=
=kRSm
-----END PGP SIGNATURE-----
--Wo19qiqIGVxkOaVEgPPs7nOPlwUAGeqca--