Skip to content

GitVersionTask caching possible? #963

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

Closed
tofutim opened this issue Jul 20, 2016 · 4 comments
Closed

GitVersionTask caching possible? #963

tofutim opened this issue Jul 20, 2016 · 4 comments

Comments

@tofutim
Copy link
Contributor

tofutim commented Jul 20, 2016

I have a Visual Studio solution with maybe 12-13 projects, each one with GitVersionTask. Normally it isn't too bad but in CI (TeamCity) each GitVersionTask takes a long time to run. Is there a way to run GitVersionTask once to get the number and just update all the assemblies with that number? Recomputing seems overkill. Also this is a tagged build, e.g., 8.0.785 - so why is it taking so long to go through the repository (which admittedly is large). Any tips or workarounds much appreciated.

@pascalberger
Copy link
Member

Which version are you using? There seems to be an issue introduced in 3.6.0 (see #942)

@tofutim
Copy link
Contributor Author

tofutim commented Jul 20, 2016

I am using 3.6.0 and I did get the feeling it was faster before. I'll check
the issue.

On Wed, Jul 20, 2016 at 11:22 AM, Pascal Berger [email protected]
wrote:

Which version are you using? There seems to be an issue introduced in
3.6.0 (see #942 #942)


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#963 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJoRp-DQGVTfQLjTRKneRs9APHImq4lks5qXmdagaJpZM4JQ44s
.

@JakeGinnivan
Copy link
Contributor

Roll back to 3.5.4 and it should fix your issue for the moment. Hope to get a fix out soon.

@asbjornu
Copy link
Member

asbjornu commented Aug 9, 2016

Just for brevity, this was fixed in #969.

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

4 participants