Continua 1.7.0.108: Finalbuilder cannot fetch from LKSLGitHub Repository any more

Continua CI Bugs
1

Related to https://www.finalbuilder.com/forums/t/cannot-find-my-dunitx-fork-any-more/6007
I'm seeing this in my logs; the "validate" button on the repo says it's OK.

I've not touched the config for ages, Simon hasn't updated much on the repo (it still has a Master branch see https://github.com/LaKraven/LKSL and https://github.com/LaKraven/LKSL/commits/master).

How can I give the .git/gitconfig for that repo?

See also http://stackoverflow.com/questions/...om-push-to

Cannot get changes for repository LKSLGitHub: Running git.exe with arguments "fetch --prune" failed with return code 128 and error output: "fatal: bad config file line 1 in .git/config"


--jeroen

2

They are somehow related.

I’ve 7zipped up the whole C:\ContinuaCI\Share tree for further investigation.

The odd thing is that many subdirectories contain both a .git and a .hg subdirectory.

Furthermore for the above Repo, the .git/config file consted more than a hundred thousands lines containing

[code][core][/code]
and one line containing

[code]quotepath = false[/code]

The repo in the previous post contained a .git/config file filled with nulls.

I’ve never seen such thing before.
Let me know where to put the 7zipped file for further investigation

A mapping between repositories and local storage would be highly appreciated, that would make tracking down this kind of stuff a truckload easier.

Furthermore the Validate button should (for existing repositories) check the validity of the underlying configuration as well.

What I’m going to try is to reset both repositories. If it still fails, I will post a reply.

--jeroen

3

Hi Jeroen,

Which version of Git is on the server ?

4

I think I understand what happened.
Continua was showing “Unknown SSL protocol error in connection to bitbucket.org:443” errors which I hadn’t monitored in a while as any 5xx errors are also in the log and flooding the log.

So I updated from “git version 1.8.5.2.msysgit.0” to “git version 2.6.1.windows.1”.

My best guess is that the old git somehow trashed 2 repos.
A reset of both repositories solved the issue.

This brings me to two feature requests:

- Have Continua CI indicate there are newer Git/Mercurial/… versions available (just like it does with newer Continua CI versions)
- Allow better display and filtering of errors in the log (I spent like 3 hours getting rid of 1000+ 5xx errors; they all look like “A new ‘Repository’ system event was logged”).

5

Hi Jeoen,

Great that you’ve got it working now.

We’ve got a task on our todo list to add filtering to the event log, though we have several higher priority features to implement before we get to that. 

We’ll keep note of your request to indicate if there are new versions of third party tools such as Git, but for now we’ll implement some code to raise an error if the older version does not support the required functionallity.

6

That’s great enough for what I’m after.
Thanks.