We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given a workflow like:
name: Test nodes: - id: jenkins executorId: jenkins data: channel: jenkins channelConfig: config: ... job: ... callMode: SYNC timeout: 1800 # ...
If the jenkins node execution times out, the corresponding notification record is correctly registered as having timeout and marked as error.
jenkins
However, the workflow itself remains in Running state and the jenkins node execution as Started.
Upon a failure, mark he node as failed and dequeue all nodes.
Have a button in the workflow to stop a workflow.
The text was updated successfully, but these errors were encountered:
#1305 Stopping workflows in case of error
930eb94
#1305 Stopping workflows in case of timeout
e13b7c4
#1305 Stopping workflow with a mutation
59958bd
#1305 Stopping a workflow in the UI
1cf5aca
#1305 Stopping a workflow
d3ddadd
Available in 4.8.78
Sorry, something went wrong.
No branches or pull requests
Given a workflow like:
If the
jenkins
node execution times out, the corresponding notification record is correctly registered as having timeout and marked as error.However, the workflow itself remains in Running state and the
jenkins
node execution as Started.Upon a failure, mark he node as failed and dequeue all nodes.
Have a button in the workflow to stop a workflow.
The text was updated successfully, but these errors were encountered: