Andreas Ericsson <ae@xxxxxx> writes:
> Daniel Pittman wrote:
>> Andreas Ericsson <ae@xxxxxx> writes:
>>> Daniel Pittman wrote:
>>>> I would like to ensure that my commits are fully bisectable before I
>>>> commit them to an upstream repository, at least to the limits of an
>>>> automatic tool for testing them.
[...]
>>> The manual step comes at merge-time; Someone has to be responsible for
>>> merging all the topics that are to be included in the release branch
>>> and make sure it builds and passes all tests after each merge.
>>
>> Ah. You have not quite grasped what I was looking for: I was after a
>> tool to help automate that step, rather than a workflow around it.
>
> Oh right. Sorry, I'm stuck in continuous-integration land where people
> tend to want the server to take care of such things.
We have that also; I am primarily motivated by avoiding trivial breakage
in the CI server, as well as bisection.
>> For example, the responsible person for that testing could use the
>> hypothetical (until someone tells me where to find it):
>>
>> git test public..test make test
[...]
> Something like this?
> --%<--%<--
> #!/bin/sh
>
> git stash
> revspec="$1"
> shift
> for rev in $(git rev-list "$revspec"); do
> git checkout $rev
> "$@" || break
> done
> --%<--%<--
>
> Run it as such:
> ./git-test.sh public..test make test
Thank you, that points me in the right direction, and I can obviously
season the rest of it to taste — reverse that revision list, for
example.
Thank you also to Wincent Colaiuta, who provided a similar script albiet
with significantly more detail.
[...]
> It doesn't handle merges very nicely, btw, but I guess this should be
> run prior to merging anyways.
Once I have the framework I can quietly work my way through fixing nasty
issues one way or another. Thanks.
Regards,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
