I am using bitbucket for my git server and am using gitversion. When I try and do a new build off the master, the build is not using the correct version. I checked the master branch on bitbucket and the correct source is there. When the build runs, gitversion indicates that the correct version is being pulled. But at the conclusion of the build, the added features in the source are not reflected in build.
Looked at the build log text file and everything seems to be as expected.
Don’t know where to go from here. I have other builds that run fine.
Bob
using Version: 1.5.0.343
here is a copy of the log with security stuff redacted.
[log removed]
Hi Bob thank you for posting.
In order to look further into this one we will need the params used for gitversion (minus the passwords), screenshots of the repository settings, and screenshots of the workflow for this one.
Please send to support@finalbuilder.com.
It’s difficult to say at the moment what is occurring. It looks as if what gitversion expected within _dynamicrepository and \Source (coming from Continua cache) are not aligned somehow.
Recently a Continua user (also a regular on these forums) has posted an article RE: using gitversion with Continua : http://geertvanhorrik.com/2014/03/27/automatically-determine-version-using-gitflow-githubflow/
Cheers.
Peter,
The issue isn’t with gitversion (I’ve been using gitversion for months now and have had no issues) but with the fact that source code that is used for the build is not the current source in bitbucket. It appears that Continua has lost sync with the bitbucket repository.
Bob
P.S. The only thing that I am using gitvaersion for is to update the assemblyinfo file with the current version of the source being built.
Hi Bob
You really haven’t given us enough to go on. What are your repository settings? What branch are you building (ie the branch shown on the changesets for the build), are you specifying the branch when running GitVersion (you removed the args so we are unable to see what you are actually doing with it). How was the build triggered (manually or via a repository changeset trigger)?
It is entirely possible that another commit may have occurred on bitbucket while Continua CI is building an earlier commit. There’s nothing we can do about that. Continua CI gets the source on the server and commits that to a cache (which is an hg repo) and then the agent pulls that cache.
If you have sensitive information that you don’t want to post here, then contact our support email address (support @ finalbuilder.com).
Just for completeness of this thread, we have worked with Bob and were able to close off the issues related to this one.
Cheers.