Uploaded image for project: 'Migration Toolkit for Applications'
  1. Migration Toolkit for Applications
  2. MTA-2001

[Custom rules in analysis] Dependency rule is not triggered

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • MTA 7.0.0
    • None
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • False
    • Yes

      Description of problem:

      False "rule was evaluated, and we did not find a violation" for a custom rules file that should be fired

      Version-Release number of selected component (if applicable):

      mta-operator-bundle-container-7.0.0-52

      How reproducible:

      100%

      Steps to Reproduce:

      Analyze tackle-test app with the following analysis configuration:

      • Source code + dependencies
      • Skip "Set targets"
      • Application and all dependencies, including known Open Source libraries
      • Upload manual rules file: 01-custom-rule-example.windup.yaml
      • No additional advanced options

      Actual results:

      Test-002-00001 (ruleID) wasn't triggered and no related migration issue was found  

      Attachments:

      01-custom-rule-example.windup.yaml
      source_with_depth_analysis_details.yaml

              rhn-engineering-dymurray Dylan Murray
              mguetta1 Maayan Hadasi
              Maayan Hadasi Maayan Hadasi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: