--NKoe5XOeduwbEQHU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 01/14 13:06, Fabian Deutsch wrote:

Hey, =20 as I learned in this patch https://gerrit.ovirt.org/#/c/50675/2 the current job templates are not suited for jobs which are run regularly but do not need to be necessarily archived, like node and the appliance.

Can't you just not add anything to exported-artifacts? that will avoid that specific job from archiving anything (for example, the check-patch and check-merged ones are not expected to generate any artifacts, usually just put there logs or reports if you want to have them after, but no need to)

=20 My first impression is that we want a new template for these kind of jobs. But I am not completely sure how these kind of job will be different from the normal template. After all we probably want those artifacts to be archived - but maybe the small difference is, that we only need _one_ build published/ in the repos. =20 Thoughts?

Maybe it would be a good idea to setup a meeting and discuss it there, as it seems to me that we are not in the same page?

=20 - fabian

--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605 --NKoe5XOeduwbEQHU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWl5CFAAoJEEBxx+HSYmnDfkMH/jaOBCv9bxBjroOV+/yK1NE+ Uwl+bVP6u6XkiHBBnP95F0Ljl1bUH4NrAKiIIU5HaTDgZ7dcVU6dKIsFcpeFIiJC j2h6NiI3MNje7yC+pyvnY2vBwd9pJaaY6SIShIZ3HxXsomrEUCUgDojQN9T685NF 2am6XBGtXlwxREM4Tugtstdvp3rucd1cSGZvTP1X9S3oL/E6ZsN+XZBr6HOjgGx5 3O5sz5Xe3fQ+UNWCRz1w6HDTacWlSuSORt9hmUYwfn2z68X9AHW0rEbEcOBUHoni Up4y/yriDHs4i7TtWZASSznRPcoa1vJRjULSuLmoqW1FAOjc8jhTeYAnBHFmWU4= =qpyf -----END PGP SIGNATURE----- --NKoe5XOeduwbEQHU--