On 04/04 11:49, Eyal Edri wrote:
On Mon, Apr 4, 2016 at 10:38 AM, David Caro Estevez <dcaro@redhat.com> wrote: =20
Hey David, as part of the migration to jenkins.phx.ovirt.org,I want to advance= with the Lago jobs. I already migrated infra-puppet/infra-docs/ovirt-node/appliance/imgbased jobs, and so = far
On 04/03 20:27, Nadav Goldin wrote: they
seem all to work. As far as I understand the Lago jobs are pretty independent so it should be rather simple. Currently there are 3 sl= aves configured (fc23, el7, fc21).
There are only 3 fc23 slaves, having one less, duplicates the check r= un time, and having only one, triplicates it, can you create new slaves instea= d of moving them from the old jenkins? (lago is not the only one using the= m, so migrating all of them is not an option)
=20 Is it possible to add new slaves with the current state of pxe not work= ing? The ideal will be to have all new servers installed with the pxe fixed = so we can deploy many more slaves. This way we can just add lots of slaves to the new jenkins. =20 We already have a template for fc23, it's just creating a new slave from =
--liqSWPDvh3eyfZ9k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 04/04 10:52, David Caro Estevez wrote: that
template (can be done from foreman too, faster than installing from scrat= ch).
Just to make sure, don't confuse lago jobs with ovirt-system tests, the ovirt-system tests use bare metal slaves, those can't be created from templ= ates so those can only be installed with pxe (or physically on site, as the virt= ual media of the ilo does not work so good)
=20
=20 =20
At the fist stage(until we finish the migration) jenkins_master_deploy-configs_merged is not running, so we could co=
ntrol
which jobs get migrated. So if a patch to the jenkins yaml will be introduced during the migration process it will have to be re-run manually.
After migrating I'll disable the lago jobs in jenkins.ovirt.org, so even if JJB runs we will have only one jenkins running the CI checks.
Don't allow both to run anything at the same time, that will lead to confusion and branches being deleted at strange times on the github repo, if th= ey run on one jenkins master, run them there only.
One more question is if there are any other jobs which are dependen=
t on the
Lago jobs(like the publishers which are dependent on all build_arti= facts on ovirt-node/appliance/node)
Lago is self-contained, anything lago needs (check-build-deploy) is t= agged as lago*, any other job that uses lago, get's it from the repos.
As far as I understand the only thing needed for migration is updat=
ing the
github api tokens and running JJB with *lago*.
And disabling the jobs on the other jenkins. The github configuration is not trivial though, the api token is vali= d only once and for a specific url. Also you have to configure the github ho= oks to point to the new jenkins (or it will not get any events), that is don= e at the github page, under project configuration.
What do you think?
Thanks
Nadav.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- 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
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
=20 =20 --=20 Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel =20 phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) =20 _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra =20 =20 --=20 David Caro =20 Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D =20 Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605
--=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 --liqSWPDvh3eyfZ9k Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXAiulAAoJEEBxx+HSYmnDgbkH/RKrJBzV9izxQjCbMqbbqb6u Fmln/5y/K3VlCdJiNgYEWMfc+olDuknqWo5Rt7hVtLlh4HPNXjgvLEzuxoQ1iTPq FA8ZGCJV/Lwx+vSlkTezShhE1N2iFAAcBWgq0Sr2wrLPOnpfY1KcCK3sCXxADzVV WVoax0cVS+FQM6rYec4ers3FCRtSCaZb5x7Mmq9gh47AubDiIzHLyou+5h4C6jp+ eJusvVmpJjbez1LnUSxHT09Lb86rYfuhRAfltcwgB1caql7/d9V6YTP6VowbRDiB MrgLfitKKbliIU9I4830Yqk/BOqBJR2hG13fg0lnOaQ96X2gVcl7f7hXonKg/ZY= =SfPV -----END PGP SIGNATURE----- --liqSWPDvh3eyfZ9k--