Some CIs like to narrow their scope to a certain set of files. For that, they specify file mask on per-job basis. So there appear annoying comments with only "Build succeeded". (an example complaint: http://lists.openstack.org/pipermail/openstack-dev/2015-June/065367.html)
Moreover, most of CIs which don't bother filtering, make lots of comments to doc/unittest changes, which is also wrong. (seehttps://review.openstack.org/#/c/152006, and most of CIs don't run unittests) What if Zuul would not comment when no real jobs run? The only meaningful task that is done is merging the patch, but anyway in case of merge failure there should be "Merge failed" comment. In case of no objections, I'll make corresponding change in zuul. -- Best regards, Evgeny Antyshev, Parallels PCS6 CI __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
