On Fri, 2015-07-17 at 23:56 +0100, Karanbir Singh wrote:
On 17/07/15 16:52, Jan Chaloupka wrote:
On 07/16/2015 10:33 AM, Karanbir Singh wrote:
On 16/07/15 00:28, Ari LiVigni wrote:
Why not continuously build the ostree based on package changes to Docker, Kub, etcd, flannel, etc. This way the triggering happens when packages are updated. It would be great if Centos had something like fedmsg or our downstream CI message bus.
this is what Colin mentioned as well, with the repo md changing we can trigger things off.
IIRC, it is not possible to detect which build has been updated. If it was kubernetes, etcd or docker? As the md file is archived, URLTrigger can not be used (with condition using xpath expresion). But this is a problem of all repo md files.
sure, and this is a good thing - a founding concept of CI is that you want to run all tests, even when the core component you care about does not change :: the idea being you validate your code still works within a changing codebase ( in this case the repo itself ).
I agree testing within the repo should be done as well for unit testing and light integration testing, but I also think doing CI of real packaged components in RPM form or in ostree is better for true CI and eventually CD IMHO.
It can be a downstream set of jobs after the repo tests are validated.
- KB