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

Using the ToolLib to download and cache the tool #11825

Merged
merged 9 commits into from
Nov 26, 2019

Conversation

navin22
Copy link
Member

@navin22 navin22 commented Nov 21, 2019

These changes will fix the bug https://github.com/MicrosoftDocs/vsts-docs/issues/6067, if the container-structure-test tool is in the same folder as the task.
Then there's a ETXTBSY error thrown as the file will be opened in node, as the tool is in the task folder.

This was happening in the hosted agents, if the tool is in the $PATH with the name "container-structure-test", it will work. Hence couldn't catch earlier.

With the toollib the tool will be in _tools folder, and it's an improvement as well we will be downloading the tool only once.

Tasks/ContainerStructureTestV0/testrunner.ts Outdated Show resolved Hide resolved
Tasks/ContainerStructureTestV0/testrunner.ts Outdated Show resolved Hide resolved
@navin22 navin22 merged commit 6164cbc into microsoft:master Nov 26, 2019
navin22 added a commit to navin22/vsts-tasks that referenced this pull request Nov 26, 2019
* Using the ToolLib to download and cache the tool
navin22 added a commit that referenced this pull request Nov 27, 2019
* Using the ToolLib to download and cache the tool (#11825)

* Using the ToolLib to download and cache the tool

* fixing the task version to be with the sprint version.
leantk pushed a commit that referenced this pull request Dec 23, 2019
* Using the ToolLib to download and cache the tool

* changing the error message.

* PR comments resolved.

* using only which with true as second argument instead of the existSync.

* Not using which to identify if tool exists. As it checks using PATH.
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

Successfully merging this pull request may close these issues.

4 participants