a7a3902ebc
Project: openstack-infra/zuul 92dc6fbcd55f6145ebb684a1060330768610a953 Ansible launcher: clean up result handling Have runJob always return a string or None for simplicity. Construct the result dictionary only when sending the work_complete packet, and send a dictionary with a result element every time, even if the value is None. Zuul will react the same whether there is no dictionary, or it has no result or the result is null, and retry the job. Finally, send a simple string as status rather than the result dictionary to ZMQ. If the job is aborted, status will be null. Change-Id: Ie093c070c2fb4baf67f538b79826a7d8e42b18d9
OpenStack Tracking Repo
zuul gates all of the contained projects in an effective single timeline. This means that OpenStack, across all of the projects, does already have a sequence of combinations that have been explicitly tested, but it's non-trivial to go from a single commit of a particular project to the commits that were tested with it.
Gerrit's submodule tracking feature will update a super project every time a subproject is updated, so the specific sequence created by zuul will be captured by the super project commits.
This repo is intended to be used in a read-only manner. Any commit in this repo will get a collection of commits in the other repos that have explicitly been tested with each other, if that sort of thing is important to you.