--sHrvAb52M6C8blB9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 04/03 20:27, Nadav Goldin wrote:
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 th= ey 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 slaves configured (fc23, el7, fc21).
There are only 3 fc23 slaves, having one less, duplicates the check run tim= e, and having only one, triplicates it, can you create new slaves instead of moving them from the old jenkins? (lago is not the only one using them, so migrating all of them is not an option)
=20 At the fist stage(until we finish the migration) jenkins_master_deploy-configs_merged is not running, so we could control 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 manuall= y. =20 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 confus= ion and branches being deleted at strange times on the github repo, if they run= on one jenkins master, run them there only.
=20 One more question is if there are any other jobs which are dependent on t= he Lago jobs(like the publishers which are dependent on all build_artifacts = on ovirt-node/appliance/node)
Lago is self-contained, anything lago needs (check-build-deploy) is tagged = as lago*, any other job that uses lago, get's it from the repos.
=20 As far as I understand the only thing needed for migration is updating 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 valid only once and for a specific url. Also you have to configure the github hooks to point to the new jenkins (or it will not get any events), that is done at t= he github page, under project configuration.
=20 What do you think? =20 =20 Thanks =20 Nadav.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=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 --sHrvAb52M6C8blB9 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXAhn9AAoJEEBxx+HSYmnDwr0H/27yKOt8SvWrATbjx7+yOn0U +pERewhkptueVsigPb6jLQnUye1gFH+ea40FjwBb5FWNDS23Hv3+kjXtKAzNAGKV iszveceqaukod1NujU+M2a8b01P9ElbgOTgZKjHEgWMEhZvyNQYezMkgjpEGqny9 5vt7jPpAu1SorYE5S+s8tRLzbk7Ttlx45XYcQnYV/Av9f13dd3x4iuoWWOujZDVe 6czuedGv7jgNn1Icyhc3IQo6fkkLY0FLaj/PgafeVAUWd8vXWEii3kHpXmsrx9tI DbACAY1M3sZzMR1M0HCJ6afIIittdvXEUuNgcDorKKERjcOmVzwogYfTders/oI= =9N4U -----END PGP SIGNATURE----- --sHrvAb52M6C8blB9--