On 19 Aug 2015, at 10:14, Paul Jakma wrote:
On Wed, 19 Aug 2015, Martin Winter wrote:
As a side note:
I would _REALLY_ like if the maintainers don’t push multiple
commits at the same time. I’m trying to run multiple (automated)
tests each time quagga master is updated, but it’s painful to go
back and pick things (manually) apart if there are multiple commits.
I would really appreciate if committers could push single commits
whenever possible.
That's presumably more "push a single commit in between runs of the CI
tool"? Can you get the CI tool to be more intelligent on this?
Let’s clarify this:
There are obviously exceptions (i.e. where multiple commits are required
for something to work), but I expect that
in this case they would be bundled as a single commit in most cases.
The CI tool (I use Atlassian Bamboo, but from my testing Jenkins works
the same way), pick up on changes in the Git
and will trigger a run. “Changes”, not a single commit. So if 10
commits are pushed, then it will only do a single
run based on the latest one. I haven’t seen a good way to change this
in any CI system.
I’m running (multiple day long) automated tests on every detected Git
change. However if something breaks,
I have to first rip my test series in small chunks (trying to pick a
single short test out of it which shows
the breakage) and then do a git bisect with it. It gets even more fun
with multiple (unrelated) bugs in the
multiple commits. If committer would push in smaller set (ideal: single
patches), then most of all this
tracking would work without my manual involvement.
(I’m also running even longer test runs for releases and every few
months and I’m currently working on a way
to run a smaller set of basic tests based on every single [new]
patchwork)
So all I ask is committers to please not stack multiple commits and push
in smaller (preferable single commits)
blocks.
- Martin
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
