Powershell Copy-Item Exit code 1
up vote
1
down vote
favorite
I have a script with several files I'd like to copy and I do it more or less like so.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
and so on.
Now I'd like this script to exit with 1 if any of the files was not copied.
Thanks in advance
powershell copy-item
add a comment |
up vote
1
down vote
favorite
I have a script with several files I'd like to copy and I do it more or less like so.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
and so on.
Now I'd like this script to exit with 1 if any of the files was not copied.
Thanks in advance
powershell copy-item
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a script with several files I'd like to copy and I do it more or less like so.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
and so on.
Now I'd like this script to exit with 1 if any of the files was not copied.
Thanks in advance
powershell copy-item
I have a script with several files I'd like to copy and I do it more or less like so.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
and so on.
Now I'd like this script to exit with 1 if any of the files was not copied.
Thanks in advance
powershell copy-item
powershell copy-item
asked Nov 11 at 12:36
Icen
15719
15719
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
What you're asking for is similar to the set -e
option in bash
, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].
PowerShell has no such option[2], but you can emulate it:
# Set up a trap (handler for when terminating errors occur).
Trap
# Print the error.
# IMPORTANT: -ErrorAction Continue must be used, because Write-Error
# itself would otherwise cause a terminating error too.
Write-Error $_ -ErrorAction Continue
exit 1
# Make non-terminating errors terminating.
$ErrorActionPreference = 'Stop'
# Based on $ErrorActionPreference = 'Stop', any error reported by
# Copy-Item will now cause a terminating error that triggers the Trap
# handler.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
# Handle failure of an external program.
foo.exe -bar
if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.
# Signal success.
exit 0
Note:
PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as
cmd
on Windows, orbash
on Unix-like platforms).PowerShell's automatic
$LASTEXITCODE
variable reflects the exit code of the most recently executed external program / PowerShell script that calledexit <n>
.Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the
trap
block, hence the explicitthrow
statement in the snippet above.- Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.
[1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105
[2] Potentially adding support for it is being discussed in this GitHub issue.
1
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
What you're asking for is similar to the set -e
option in bash
, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].
PowerShell has no such option[2], but you can emulate it:
# Set up a trap (handler for when terminating errors occur).
Trap
# Print the error.
# IMPORTANT: -ErrorAction Continue must be used, because Write-Error
# itself would otherwise cause a terminating error too.
Write-Error $_ -ErrorAction Continue
exit 1
# Make non-terminating errors terminating.
$ErrorActionPreference = 'Stop'
# Based on $ErrorActionPreference = 'Stop', any error reported by
# Copy-Item will now cause a terminating error that triggers the Trap
# handler.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
# Handle failure of an external program.
foo.exe -bar
if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.
# Signal success.
exit 0
Note:
PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as
cmd
on Windows, orbash
on Unix-like platforms).PowerShell's automatic
$LASTEXITCODE
variable reflects the exit code of the most recently executed external program / PowerShell script that calledexit <n>
.Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the
trap
block, hence the explicitthrow
statement in the snippet above.- Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.
[1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105
[2] Potentially adding support for it is being discussed in this GitHub issue.
1
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
add a comment |
up vote
1
down vote
accepted
What you're asking for is similar to the set -e
option in bash
, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].
PowerShell has no such option[2], but you can emulate it:
# Set up a trap (handler for when terminating errors occur).
Trap
# Print the error.
# IMPORTANT: -ErrorAction Continue must be used, because Write-Error
# itself would otherwise cause a terminating error too.
Write-Error $_ -ErrorAction Continue
exit 1
# Make non-terminating errors terminating.
$ErrorActionPreference = 'Stop'
# Based on $ErrorActionPreference = 'Stop', any error reported by
# Copy-Item will now cause a terminating error that triggers the Trap
# handler.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
# Handle failure of an external program.
foo.exe -bar
if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.
# Signal success.
exit 0
Note:
PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as
cmd
on Windows, orbash
on Unix-like platforms).PowerShell's automatic
$LASTEXITCODE
variable reflects the exit code of the most recently executed external program / PowerShell script that calledexit <n>
.Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the
trap
block, hence the explicitthrow
statement in the snippet above.- Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.
[1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105
[2] Potentially adding support for it is being discussed in this GitHub issue.
1
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
What you're asking for is similar to the set -e
option in bash
, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].
PowerShell has no such option[2], but you can emulate it:
# Set up a trap (handler for when terminating errors occur).
Trap
# Print the error.
# IMPORTANT: -ErrorAction Continue must be used, because Write-Error
# itself would otherwise cause a terminating error too.
Write-Error $_ -ErrorAction Continue
exit 1
# Make non-terminating errors terminating.
$ErrorActionPreference = 'Stop'
# Based on $ErrorActionPreference = 'Stop', any error reported by
# Copy-Item will now cause a terminating error that triggers the Trap
# handler.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
# Handle failure of an external program.
foo.exe -bar
if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.
# Signal success.
exit 0
Note:
PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as
cmd
on Windows, orbash
on Unix-like platforms).PowerShell's automatic
$LASTEXITCODE
variable reflects the exit code of the most recently executed external program / PowerShell script that calledexit <n>
.Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the
trap
block, hence the explicitthrow
statement in the snippet above.- Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.
[1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105
[2] Potentially adding support for it is being discussed in this GitHub issue.
What you're asking for is similar to the set -e
option in bash
, which causes a script to exit instantly in the event that a command signals failure (except in conditionals)[1].
PowerShell has no such option[2], but you can emulate it:
# Set up a trap (handler for when terminating errors occur).
Trap
# Print the error.
# IMPORTANT: -ErrorAction Continue must be used, because Write-Error
# itself would otherwise cause a terminating error too.
Write-Error $_ -ErrorAction Continue
exit 1
# Make non-terminating errors terminating.
$ErrorActionPreference = 'Stop'
# Based on $ErrorActionPreference = 'Stop', any error reported by
# Copy-Item will now cause a terminating error that triggers the Trap
# handler.
Copy-Item xxx1 yyy1 -Force
Copy-Item xxx2 yyy2 -Force
Copy-Item xxx3 yyy3 -Force
Copy-Item xxx4 yyy4 -Force
# Handle failure of an external program.
foo.exe -bar
if ($LASTEXITCODE -ne 0) Throw "foo failed." # Trigger the trap.
# Signal success.
exit 0
Note:
PowerShell-internally, exit codes are not used in error handling; they typically only come into play when invoking external programs from PowerShell, or when PowerShell / a PowerShell script needs to signal success vs. failure for the outside world (when called from another shell, such as
cmd
on Windows, orbash
on Unix-like platforms).PowerShell's automatic
$LASTEXITCODE
variable reflects the exit code of the most recently executed external program / PowerShell script that calledexit <n>
.Calls to external (console/terminal) programs that signal failure via a nonzero exit code do not trigger the
trap
block, hence the explicitthrow
statement in the snippet above.- Unless you set the exit code explicitly, it is the exit code of whatever external program happened to execute last that determines the script's overall exit code.
[1] Note that this option has its critics, because the exact rules around when a failure is tolerated and when it causes a script to abort are hard to remember - see http://mywiki.wooledge.org/BashFAQ/105
[2] Potentially adding support for it is being discussed in this GitHub issue.
edited Nov 11 at 21:11
answered Nov 11 at 12:51
mklement0
123k20235265
123k20235265
1
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
add a comment |
1
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
1
1
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
My pleasure, @Icen; glad to hear it was helpful.
– mklement0
Nov 13 at 12:32
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53248823%2fpowershell-copy-item-exit-code-1%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown