Hi again,
quite a while ago I wrote about Continua not registering git commits if their author date lay before that of the latest commit known to Continua. While these commits now show up in the Changes overview for a Continua build they do not appear to be distributed to the build agents. In the attached screenshot you can see the commits as they are shown in the changes view. I have also attached a git log for these three commits.
As you can see from the log the author date of the the commit 93d2821ca368f3025b3609e5f50d8d0b63853693 lies a few days before the others. But the commit date is later. The changes made in that commit however are not reflected in the files that our build agents use. They are still the same as they were with commit 3b762f94e91a45434473961a8dd93636c075e30f.
If you need any more information I’ll be happy to provide it but we have not been able to reproduce this error at will yet so it may take a while.
Hope this can be fixed soon.
Regards,
Christoph
Btw. the attached “gitlog.jpg” is actually a text file but these fine forums wouldn’t allow me to upload those.
Hi Christoph,
The commits are ordered in topological order e.g. in the order
git log --topo-order --allWe should be building the first commit on the results of that command. Can you confrim whether this is the case or not?
The git commits are in the expected when running that command. I also checked the mercurial log of Continua’s internal repository and all three commits are present with roughly accurate commit dates.
changeset: 39:4fb13c0341e5
branch: develop
user: Continua
date: Mon Oct 12 13:52:32 2015 +0200
summary: Automated commit by Continua CI from ‘ACMP’ repository for revision ‘93d2821ca368f3025b3609e5f50d8d0b63853693’. Comment: DevExpress 15.1.5 update.
changeset: 38:f6f00d0f6d53
branch: develop
user: Continua
date: Mon Oct 12 13:34:00 2015 +0200
summary: Automated commit by Continua CI from ‘ACMP’ repository for revision ‘3b762f94e91a45434473961a8dd93636c075e30f’. Comment: no header in sections tree.
changeset: 37:375be007ce94
branch: develop
parent: 35:a2f620edc7ab
user: Continua
date: Mon Oct 12 13:14:27 2015 +0200
summary: Automated commit by Continua CI from ‘ACMP’ repository for revision ‘d2e650427cb51f048c730c46c3919d5c8b44a72c’. Comment: Merge branch ‘feature/itam-50’ into ‘develop’.
After another commit was made in the same branch the build agents now correctly get the latest changes again so we currently cannot reproduce the error any more.
Can you run the following query on the database and send the relevant results to support@finalbuilder.com?
SELECT c.*FROM builds_changeset c INNER JOIN builds_repository r ON r.id = c.repositoryId WHERE r.Name = ‘YourRepoName’ ORDER BY ordernumber DESC;The connection details for the database is in C:\Program Files\VSoft Technologies\ContinuaCI\Server\Continua.Server.Service.exe.config under hibernate-configuration -> session-factory -> property name=“connection.connection_string”. If your sing the bundle PostgreSQL databse, run the query using C:\Program Files\VSoft Technologies\ContinuaCI\Server\PostgreSQL\bin\pgAdmin3.exe.
I’m particularly interested in the ordernumber field and whether this matches the topological order of the commits
Note that it is the database ordering that use to pick the changeset to build rather than the ordering of commits in the repository cache.