-
Notifications
You must be signed in to change notification settings - Fork 63
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
[ISSUE]: Unable To Run Commands On Azure DevOps #1336
Comments
I am also having this issue. I am upgrading from
Error:
EDIT: For me at least it seems to be a problem with the v6 spec. Targetting v5 works as expected:
|
Yup, I've just gone back to try that (it didn't work first time) but looks like it has this time round, targeting 5.x (Downloading 5.12) Edit - just tried it on a different service with a large number of branches, and it failed with the error 'stdout maxBuffer length exceeded', so looks like it doesn't always work with v3 / 5.x |
Closed by #1278 |
@arturcic I've tried the new version (3.0.2) and it worked at v3 / 5.12, for one of our repos. However, it still failed with the buffer issue for another one. That one has got a lot of stale release branches (around 100 or so) - is the recommendation to clean up or tag them off, to reduce the amount of work the tool has to do? |
@bendursley yes, that is the recommendation, that will also speed up the running time of the tool as well |
@arturcic Will tagging the release branches off be ok? Or will that leave us in the same situation? (IE - we should just delete the release branches) Thanks for your help! |
tagging might help in terms of finding the version base, but that could still not improve much the max buffer situation, better to clean it up if possible |
Prerequisites
GitVersion package
AzureDevops task
GitVersion version
6.0.0 - 6.0.5
Operating system
Windows, Linux
What are you seeing?
We've got a set up where we use a GitVersion YML template file. We've been on v0 of the ADO tasks and 5.12 spec for quite some time and have finally upgrades to v3 \ 6.x, but now we're just getting 'Command Failed' on both Ubuntu and Windows, and the error messages aren't clear to the issue.
What is expected?
Git Version correctly runs
Steps to Reproduce
Above tasks cause an issue, using them
RepositoryFixture Test
No response
Output log or link to your CI build (if appropriate).
The text was updated successfully, but these errors were encountered: