On Thu May 27 19:40:02 2010, XENO wrote:
Show quoted text> I don't really want CommitBuild to commit anytime I build. However after
> a successful passing of dzil test would be ok, or maybe after a
> successful test if and only if the branch the build is based on has a
> newer commit.
i'm not a big fan of commitbuild either, which is why i did not put this
plugin as part of @git. in fact, it has been contributed by brian (that
i added in cc:), i just merged the results.
==> brian, what do you think of xeno's ideas?
i think that detecting whether there's a newer commit is a sensible
idea. i'm less sure regarding needing tests to pass: one may not want to
run a long test suite, or maybe needs help regarding failing tests...
so, can you guys brainstorm about a sensible behaviour? if the needs are
really different, it's also possible to rename commitbuild to sthg else
(commitbuildtree or whatever), with a parameter specifying when the
commit should happen, after build or after test.
in any cases, i'm welcoming any pull requests, so don't hesitate to code
it your way. code is available at github.com/jquelin/dist-zilla-plugin-git
note that since i'm not that much interested in this plugin, i'm just
making sure tests pass for it, but don't concentrate that much on
evolving its features. i'd rather merging pullreqs. :-)