Most jobs in our pipelines update an independant dashboard. In order to mark a particular job as failed, we need to use the runif element extensively. The configuration reference states:
"If <runif> is under <exec> while the <exec> has some <arg>s, the <runif>s should be defined before <arg>"
However, Go 2.1.0 re-orders the runif and arg tags, whether editting the job, stage, pipeline or server xml.... I have 2 code snippets below. The first one is the one I enter into the UI, and the 2nd is the the one that results after saving and re-editting.
This seems to cause runif's to not be parsed correctly. In addition, is there a way to configure runif's to run a set of tasks if passed and a different set if failed?
e.g. <runif status="failed"><exec command="command1" /><exec command="command2"></runif>
Code Snippet
UI re-ordering runif / arg of an exec task and runif logic
Comments
1 comment
For reference, I opened a support ticket and created some specific use-cases for this. The runif parameter is parsed correctly, regardless of the order.
To confirm the response:
"We will update the documentation to remove the constraint on ordering. The order does not affect the behavior in this case."
Please sign in to leave a comment.