Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discrepencies between GitVersion CommandLine and GitVersionTask #460

Closed
jonathannaim opened this issue Jun 9, 2015 · 7 comments
Closed

Comments

@jonathannaim
Copy link

Hello,

I've just upgraded to latest version 3.0.0-beta0003 for both.

When running GitVersionTask during the build I get the following error message on a release branch :

35>MSBUILD : warning : Could not determine assembly version: Path '****' doesn't point at a valid Git repository or workdir.

Whereas when I run GitVersion I get correct information:

C:\Users\Jonathan\Source\Repos\****>gitversion
{
  "Major":0,
  "Minor":1,
  "Patch":0,
  "PreReleaseTag":"beta.1",
  "PreReleaseTagWithDash":"-beta.1",
  "BuildMetaData":2,
  "FullBuildMetaData":"2.Branch.release/0.1.0.Sha.0eabeb44abe4b64d35cb09c569c01f8b93c52a50",
  "MajorMinorPatch":"0.1.0",
  "SemVer":"0.1.0-beta.1",
  "LegacySemVer":"0.1.0-beta1",
  "LegacySemVerPadded":"0.1.0-beta0001",
  "AssemblySemVer":"0.1.0.0",
  "FullSemVer":"0.1.0-beta.1+2",
  "InformationalVersion":"0.1.0-beta.1+2.Branch.release/0.1.0.Sha.0eabeb44abe4b64d35cb09c569c01f8b93c52a50",
  "BranchName":"release/0.1.0",
  "Sha":"0eabeb44abe4b64d35cb09c569c01f8b93c52a50",
  "NuGetVersionV2":"0.1.0-beta0001",
  "NuGetVersion":"0.1.0-beta0001",
  "CommitDate":"2015-06-09"
}

Any idea what's going on? Could it be a setup issue on my side?

Thanks!

Jonathan

@JakeGinnivan
Copy link
Contributor

More likely I have broken the task 😞

Will see if I can get beta.4 out tonight which fixes this issue.

@jonathannaim
Copy link
Author

Wow Thanks!

I take the opportunity to tell you guys that GitVersion is GOLD!

@Sacrelicious
Copy link

Is there any update on getting an updated beta out?

@JakeGinnivan
Copy link
Contributor

Sorry, I have not had a chance to fix this. Any help/pr's appreciated, otherwise will get to it as soon as I can (probably tomorrow)

@Sacrelicious
Copy link

I may have time to try to get a PR for this. It sounded like you had an idea of what was going on, if so, could you point me in the direction of a good place to start debugging?

@JakeGinnivan
Copy link
Contributor

I don't know what the issue is, but I made a lot of changes around that area and we don't have that many tests.

@JakeGinnivan
Copy link
Contributor

Will be fixed in beta4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants