-
Notifications
You must be signed in to change notification settings - Fork 61
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
Azure Pipeline Task gitversion/setup@0
0.10.0
does not work
#815
Comments
I can confirm that I'm having the same issue as of this morning. |
Confirming this. Looks like the azure agents don't have version 0.10.0 installed on them. Seems like there isn't a way to force it to use the previous working version of 0.9.15 |
I will have a look and test it myself |
Confirming this. 2023-03-11T10:42:52.6681398Z ##[debug]Evaluating condition for step: 'Install GitVersion 5.8.1' |
Ok I can confirm, I will check the issue, for now it's not needed to confirm anymore |
Is it possible to specify and older version in our pipeline some how. This is now blocking a high priority release. |
I am facing the same issue after Azure DevOps automatically updated the GitTools extension to the latest version (11th of March 5:36 am UTC) |
The same issue |
I will revert the changes and release a new version |
Then it needs more investigation, and a way to test it before publishing a new version |
As a work around you can modify your pipeline to specify the task version to download:
|
That is correct, I forgot about this |
so basically you pin to a specific version |
Meanwhile I found the source of the issue - |
same issue. |
version 0.10.2 published, please give it a try |
it'ok 2023-03-11T13:19:06.8744480Z ##[debug]Evaluating condition for step: 'Install GitVersion 5.8.1' 2023-03-11T13:19:11.7322744Z Caching tool: GitVersion.Tool 5.8.1 x64 |
It worked, thanks for the fast update |
Thank you for confirmation, then I can close this one. As a recommendation - pin the task version for your pipelines, and only try the latest version when there is no risk of disturbing the releases |
Thanks for fixing this and for maintaining this project! |
This new version doesn't seem to work in an on-prem scenario...?
|
Looks like you are still using |
you're using |
Did you "Re-run failed jobs" instead of starting a new build? Try starting a new build instead of re-running the failed one |
I did. But I as is I figured it's not critical and I can wait till Monday. Hopefully whatever caching / scheduling issue might be responsible for the current version being "frozen" will get resolved by then. |
Re-running will use the old/previous version. You need to run a new pipeline. It is working now! Thank you |
I just saw my DevOps server updated the extension, and it's working fine now. :) |
I'm getting a very strange error "network socket disconnected before secure TLS connection was established" when it tries to install version 0.10.2. The old version 0.9.15 doesn't give this. |
Job Info:
gitversion/setup@0:
The text was updated successfully, but these errors were encountered: