I'm using the trigger-pipeline pipe to tigger and monitor other pipelines. I'm currently on v4.0.5.
I just saw a result where the trigger-pipeline returned success even though the pipeline it ran failed with a system error:
INFO: Attempt number 97: Build number 798 for alertremote is IN_PROGRESS, waiting for pipeline to finish...
INFO: Attempt number 98: Getting build info.
✔ Build number 798 for alertremote@develop finished with result ERROR.
✔ Pipe finished successfully.
The json returned by that pipeline has this state info:
"state": {
"type": "pipeline_state_completed",
"name": "COMPLETED",
"result": {
"type": "pipeline_state_completed_error",
"name": "ERROR"
}
}
I know I'm using an older version of the pipe, but I checked the latest version of the trigger-pipeline code in the repo and it doesn't appear this case is accounted for in the latest version either. Can this be fixed?
@Jay Seletz I believe, the updated pipe 4.1.5 can solve this issue, welcome to try out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Jay Seletz right, this is a bug in the pipe, which we are gonna fix asap. Thanks for reporting this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.