You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2024. It is now read-only.
If the $destination_file variable is set then the PowerShell script should use that variable instead of getting the filename from the URL.
In my case, I'm downloading two files with the same name in the URL (two different files that happens to have the same name in the URI) which causes the content of this file be constantly rewritten. Since there is a dependency between that file and the downloading, the files get redownloaded each time the agent runs.
The text was updated successfully, but these errors were encountered:
+1 to this, I've just run into the problem myself because MS labels x64 files the same way as x86 meaning I need the powershell scripts (and the downloaded files) to be different names.
In fact, why is there a separate powershell script per download? Wouldn't it be neater to store only one download script and just call it with params?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If the
$destination_file
variable is set then the PowerShell script should use that variable instead of getting the filename from the URL.In my case, I'm downloading two files with the same name in the URL (two different files that happens to have the same name in the URI) which causes the content of this file be constantly rewritten. Since there is a dependency between that file and the downloading, the files get redownloaded each time the agent runs.
The text was updated successfully, but these errors were encountered: