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

Incorrect version number shown in artifacts #59

Closed
gep13 opened this issue Jul 10, 2015 · 6 comments
Closed

Incorrect version number shown in artifacts #59

gep13 opened this issue Jul 10, 2015 · 6 comments
Assignees
Labels
Milestone

Comments

@gep13
Copy link
Member

gep13 commented Jul 10, 2015

As seen here:

image

and here:

image

For the images shown above, it should be showing 0.3.0.

@gep13 gep13 added the Bug label Jul 10, 2015
@gep13 gep13 added this to the 0.4.0 milestone Jul 10, 2015
@gep13 gep13 self-assigned this Jul 10, 2015
@gep13
Copy link
Member Author

gep13 commented Jul 10, 2015

@GeertvanHorrik @JakeGinnivan when running the build on AppVeyor, I am using the /UpdateAssemblyInfo true flag, so the compiled assembly should be using the generated semantic version number, but looks like this isn't happening. Any thoughts on what could be going on here? Cheers!

This is where I am executing GitVersion on AppVeyor:

https://github.com/GitTools/GitReleaseManager/blob/develop/BuildScripts/default.ps1#L418

@JakeGinnivan
Copy link

If you are using the commonassemblyinfo trick then those attributes won't exist in each assemblyinfo file. You will need to specify the file name

Sent from my Windows Phone


From: Gary Ewan Parkmailto:notifications@github.com
Sent: ‎11/‎07/‎2015 2:51 AM
To: GitTools/GitReleaseManagermailto:GitReleaseManager@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [GitReleaseManager] Incorrect version number shown in artifacts (#59)

@GeertvanHorrikhttps://github.com/GeertvanHorrik @JakeGinnivanhttps://github.com/JakeGinnivan when running the build on AppVeyor, I am using the /UpdateAssemblyInfo true flag, so the compiled assembly should be using the generated semantic version number, but looks like this isn't happening. Any thoughts on what could be going on here? Cheers!

This is where I am executing GitVersion on AppVeyor:

https://github.com/GitTools/GitReleaseManager/blob/develop/BuildScripts/default.ps1#L418


Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-120493085.

@gep13
Copy link
Member Author

gep13 commented Jul 11, 2015

I am not using that technique, just straight up AssemblyInfo files in each project.

gep13 referenced this issue in gep13/GitReleaseManager Jan 2, 2016
gep13 referenced this issue in gep13/GitReleaseManager Jan 8, 2016
- GitVersion was being executed from the BuildScripts folder, therefore there were no AssemblyInfo files to update
- By passing in rootDirectory as the first parameter, it will be able to find and update the correct attributes
gep13 referenced this issue in gep13/GitReleaseManager Jan 8, 2016
gep13 referenced this issue in gep13/GitReleaseManager Jan 8, 2016
gep13 referenced this issue in gep13/GitReleaseManager Jan 8, 2016
gep13 referenced this issue in gep13/GitReleaseManager Jan 8, 2016
- GitVersion was being executed from the BuildScripts folder, therefore
there were no AssemblyInfo files to update
- By passing in rootDirectory as the first parameter, it will be able to
find and update the correct attributes
gep13 added a commit that referenced this issue Jan 8, 2016
(GH-59) Getting versioning working correctly
@gep13
Copy link
Member Author

gep13 commented Jan 8, 2016

@JakeGinnivan figured out what the issue was here.

GitVersion was being executed from within my BuildScripts folder, therefore there were no AssemblyInfo files downwind of that folder. Passed in the rootDirectory as the first parameter to GitVersion, and everything ended up working. Took me a minute to figure out what was going on though!

@gep13 gep13 closed this as completed Jan 8, 2016
@JakeGinnivan
Copy link

Nice find

@gep13
Copy link
Member Author

gep13 commented Jan 9, 2016

@JakeGinnivan took me quite a while to figure it out, and at one point I was tearing out what little is left of my hair, but eventually it all became clear 😄

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

No branches or pull requests

2 participants