The repositories have various branches, some really old that do not even run the tests the same way we do it now. So we have never built those branches here in jenkins. And it seems it tries to build some of those branches too, from time to time.

The collection of revisions is made from old to new (in that order) to "be fair". I've made a patch that just changes the order of the list and seems to work around this (just a reverse), so if the last element (the newest) is in the list, it should be what I want to build. And in fact, it seems to fix it. But if the list has more than one element, I don't know why it doesn't continue building the others and fails later, building some never built branches.

The patch is here: https://github.com/rata/git-plugin/commit/3c9409e79d9fa73780a15da3814af330ca13cc77

I've not investigated further since this actually works around the problem for me. But knowing this could be useful to understand the real bug =)

I think we don't want to build "all non-built" branches, even if they didn't change. I think we should build only the branches that has changes, so we should probably fix something to filter those branches of the "revs" list (asuming they are there, I don't even look at the content of "revs" :-D)

Please let me know if you want me to test something

Thanks a lot,
Rodrigo

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to