[CentOS-devel] integrating cbs.centos.org repos with ci jobs at ci.centos.org

Fri Aug 14 11:59:20 UTC 2015
Fabian Arrotin <arrfab at centos.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/08/15 11:08, Karanbir Singh wrote:
> hi guys, Can we get some notes on the wiki ( maybe in the
> GettingStarted guide for the CI users ), on how they can track the
> cbs repos for new content and trigger builds from there.
> 
> I know we do this already for the cloud-sig, openstack packstack 
> validation run, but its a feature that we can use in quite a few
> places.
> 
> Regards,
> 

So there were multiple discussions, including some about a message bus
(and mainly a discussion about fedmsg) that would be used between
koji/cbs and jenkins/ci.
The interim solution (that doesn't need anything else than a plugin at
the Jenkins side) is to just "watch" some repositories from CBS and
trigger some tests directly through Jenkins when new packages/repodata
are generated.

The plugin that is now installed on ci.centos.org is the following one
: https://wiki.jenkins-ci.org/display/JENKINS/URLTrigger+Plugin

Then, some jobs (like
cloud-sig-validate-packstack-rdo-kilo-testing_tag/) are configured to
"watch" some repositories, and then be triggered when it changed .

See for example the
https://ci.centos.org/job/cloud-sig-validate-packstack-rdo-kilo-testing_tag/31/triggerCauseAction/
job log, showing the trigger as repodata/repomd.xml was different

Depending on the integration between koji and ci env, we can continue
to use that one, or then switch to a "message queue" oriented solution.

We can start writing a dedicated page on the wiki, to consolidate all
the current plugins/triggers that one project can use for that, and
then also giving ideas to existings or new projects using the ci infra.

- -- 
Fabian Arrotin
The CentOS Project | http://www.centos.org
gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAlXN2BgACgkQnVkHo1a+xU4X7ACfSFT3LUhz7/52TdYdKajawR1u
AWkAnjYpNf5yS7oDhBQNjU/9Ao8gqn5E
=SJvJ
-----END PGP SIGNATURE-----