Skip to content

Added retry on TFVC getSources step #3016

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

shkiltos
Copy link
Contributor

Number of Azure DevOps customers are facing connection issue while building tfvc project. They are getting 503 on getSources step. Added a retry on this step

@ghost
Copy link

ghost commented Jun 16, 2020

CLA assistant check
All CLA requirements met.

throw;
}
}
await Task.Delay(delay);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this approach will add retries to everything, not just TFVC operations. I think a better approach would be to handle this in the TFVC CLI manager. I already did this for gets, but if we need it in more operations it should be pretty easy to build off of my pr here - #2972

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding on this, were you able to repro the issue that users were facing?

I'm concerned that error was due to the naming of the workspace folder and if so a retry wouldn't work.

Let me know what you think.

Copy link
Contributor Author

@shkiltos shkiltos Jun 18, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Error happens from time to time, wouldn't naming of the workspace problem cause failure constantly? Anyways, retry didn't work out. In the most recent agent the same error happens

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shkiltos let's discuss offline, feel free to ping me

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@shkiltos to follow up, I don't think this is the right approach, I think we'd be better served handling this directly in the TFVC CLI Manager, rather than retrying everything

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

Successfully merging this pull request may close these issues.

4 participants