We are having periodic problems recently with git interacting badly with continua.
Last week continua decided that a random 3 month old changeset was ‘latest’ and it tried to build old code. Reset did not make any difference. Eventually I had to delete and recreate the repository entry, which cleared the problem.
Just now the entire system stuck ‘Associating changesets with the build’ which blocked every compile until we ran out of agents. That was solved with a reset.
It seems something is odd with the changeset mechanism. Is it just ‘git log origin…HEAD’ or is it doing something more complex?
Hi Tony,
We would need some more information to investigate your issue. Can you provide details of any specific repository settings you have selected? Can you also check the Changes tab on the configuration page and see if there is an error logged against the latest changeset for the problematic repository? Additionally, can you check the Administration - Event Log page for errors related to this repository?
If there are no errors logged then we would need to see a debug log. Ensure that you restart the server and commit a new changeset after enabling debug logging and wait until the issue is reproduced. The debug log will also show you the many Git commands that we use (git fetch, git log, git checkout, git clean, git status, git config, git branch, git remote update, git for-each-ref, git show, git add, git diff, git reset, git submodule init, git submodule update, git tag).
Make sure you have the latest version installed - we fixed an issue in v1.8.1.322, for example, where the latest changeset would be missed if the checkout process takes a long time and the build was manually started while the previous changeset was still in the process of being checked.
You can send the debug log and other information to support@finalbuilder.com rather than posting your system details publicly on this forum.