Open Stack

On Mon, Mar 24 2014, John Dennis wrote:

> But from that point forward it appears as if each commit is handled
> independently rather than being an ordered list of commits that are
> grouped together sharing a single review where their relationship is
> explicit. Also the jenkins tests either needs to apply all the commits
> in sequence and run the test or it needs to run the test after applying
> the next commit in the sequence.
>
> Can someone provide some explanation on how to handle this situation?
>
> Or perhaps I'm just not understanding how the tools work when multiple
> commits are submitted.

If a patch depends on another one, Jenkins is run with all the needed
patches applied.

-- 
Julien Danjou
;; Free Software hacker
;; http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140324/340a4084/attachment.pgp>