在失败的任务上继续执行Azure Pipeline

Question

I have a task that runs Cypress:

-ErrorAction SilentlyContinue
cd $(System.DefaultWorkingDirectory)/_ClientWeb-Build-CI/ShellArtifact/
npx cypress run

And I've set the ErrorActionPreference to continue . But when my Cypress fails:

##[error]PowerShell exited with code '1'.

The next task is canceled and the release failed. How do I continue the release even Cypress failed, and is it possible to give a boolean a true/false value based on the Cypress task result?

Answer 1

you can put a condition on the subsequent tasks to work even if previous tasks failed.

jobs:
- job: Foo

  steps:
  - powershell: |
      your code here
  - script: echo Hello!
    condition: always() # this step will always run, even if the pipeline is cancelled

- job: Bar
  dependsOn: Foo
  condition: failed() # this job will only run if Foo fails

https://docs.microsoft.com/en-us/azure/devops/pipelines/process/expressions?view=azure-devops#job-status-functions
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/conditions?view=azure-devops&tabs=yaml

Answer 2

The ErrorActionPreference option is used to determine whether to continue to execute rest code instead of task. So, with continue value for ErrorActionPreference , the task will execute next line code of your script even through current line code throws error, unless you call exit .

For your requirement, you are using release pipeline (it is UI designer), and you want to continue to run whole release, so, you just need to check Continue on error option:

Answer 3

如果即使Cypress任务失败，也要继续发布，只需将以下行添加到Cypress任务中：

continueOnError: true 

Answer 4

The argument "ErrorActionPreference" is used to setting whether the code inside this script execute with errors or not, it can't control the next task.

You can add a condition in the end of the subsequent tasks.

condition: always() # this step will always run, even if the pipeline is cancelled

Or you can add an argument setting to the error task.

continueOnError: true # 'true' if future steps should run even if this step fails; defaults to 'false'

Hope this can help you!