Re: [ovirt-devel] The engine build job you probably didn't know exists
On Wed, Dec 7, 2016 at 4:39 PM, Eyal Edri <eedri(a)redhat.com> wrote:
FYI,
After hearing that this might be useful to many developers, I wanted to
bring to your attention the ovirt-engine master build job from patch [1]
which allows you to build new rpms from an open ovirt-engine patch on
Gerrit.
Its was created as temp job for a team who needed it a few months ago, but
seems it might useful for other teams as well, so we decided to publish it
even though its not standardized yet as part of our standard CI system.
I hope you can find it useful for your teams.
Never heard about it, sounds useful.
We have too many jobs (for me) to know them all.
So I use 'search'. What to search for? Usually the project name, but some
projects have many jobs too.
There are jobs named something_manual, 87 currently. Some (many? all?
those I know) get a tarball as input. I don't like this personally,
as I can't know, when using a result of such a job, what was in the
tarball. Much better to have to push first to gerrit and supply
that (or commit hash, or something like that).
Some of them are called something_any_something_manual. Are these
special? What's 'any'?
Perhaps we can have (instead? in addition?) a button on gerrit
"trigger build-artifacts" that will run the standard-CI build-artifacts?
Or some other new script we'll add to standard-CI? Because current
build-artifacts is expected to be ran only after merge, and the
publisher reads it. Perhaps e.g. "build-scratch-artifacts".
[1]
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_...
--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
Didi