The YML Parser Callisto is using doesn’t respect the order - it seems like it uses a Set internally instead of an Array. Additionally when two conflicting rules are applied it matches a random one which could lead to a failed build later in the pipeline. Correctly apply all silencing rules instead of the first matching one.
Tasks
[x] filter every rule from config.yml instead of first matching one
Description
The YML Parser Callisto is using doesn’t respect the order - it seems like it uses a Set internally instead of an Array. Additionally when two conflicting rules are applied it matches a random one which could lead to a failed build later in the pipeline. Correctly apply all silencing rules instead of the first matching one.
Tasks
config.ymlinstead of first matching one