hi,
Is there anyway to add jenkins job triggers based on new package builds from cbs.centos.org ? I thought it might be just as simple as tracking the repomd.xml file under cbs.centos.org/repos/<intended repo>/os/repodata - but that file is redone every hour, regardless of new builds or not.
is there another way to track these ? rather than having to write a koji plugin ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 19/05/15 14:30, Karanbir Singh wrote:
hi,
Is there anyway to add jenkins job triggers based on new package builds from cbs.centos.org ? I thought it might be just as simple as tracking the repomd.xml file under cbs.centos.org/repos/<intended repo>/os/repodata - but that file is redone every hour, regardless of new builds or not.
is there another way to track these ? rather than having to write a koji plugin ?
If you want to track specific packages (to trigger specific jobs in Jenkins) , why not verifying the md5sum/sha256sum of those packages, compare with previous ones (from last check) and then trigger a jenkins build if not equal ? Don't know if koji has such plugin to itself do an action (that could be the trigger for jenkins)
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 19/05/15 13:36, Fabian Arrotin wrote:
On 19/05/15 14:30, Karanbir Singh wrote:
hi,
Is there anyway to add jenkins job triggers based on new package builds from cbs.centos.org ? I thought it might be just as simple as tracking the repomd.xml file under cbs.centos.org/repos/<intended repo>/os/repodata - but that file is redone every hour, regardless of new builds or not.
is there another way to track these ? rather than having to write a koji plugin ?
If you want to track specific packages (to trigger specific jobs in Jenkins) , why not verifying the md5sum/sha256sum of those packages, compare with previous ones (from last check) and then trigger a jenkins build if not equal ? Don't know if koji has such plugin to itself do an action (that could be the trigger for jenkins)
not packages, tracking the repo for new packages or updates to existing ones.
On 05/19/2015 02:30 PM, Karanbir Singh wrote:
hi,
Is there anyway to add jenkins job triggers based on new package builds from cbs.centos.org ? I thought it might be just as simple as tracking the repomd.xml file under cbs.centos.org/repos/<intended repo>/os/repodata - but that file is redone every hour, regardless of new builds or not.
It's not the case anymore since I added a mechanism to cache (few weeks ago). You can check the timestamps.
However it seems I didn't push the change to cbs-tools so it make sense nobody knew. Corrected: https://git.centos.org/commit/sig-core!cbs-tools.git/39bd31f98db80e6a5de482f....
On 19/05/15 14:10, Thomas Oulevey wrote:
On 05/19/2015 02:30 PM, Karanbir Singh wrote:
hi,
Is there anyway to add jenkins job triggers based on new package builds from cbs.centos.org ? I thought it might be just as simple as tracking the repomd.xml file under cbs.centos.org/repos/<intended repo>/os/repodata - but that file is redone every hour, regardless of new builds or not.
It's not the case anymore since I added a mechanism to cache (few weeks ago). You can check the timestamps.
However it seems I didn't push the change to cbs-tools so it make sense nobody knew. Corrected: https://git.centos.org/commit/sig-core!cbs-tools.git/39bd31f98db80e6a5de482f....
oh fantastic! this really makes things easier.
-
Fabian Arrotin -
Karanbir Singh -
Thomas Oulevey