[chromeperf] update conditions for catapult try jobs

The current logic runs catapult try jobs even if changes are only in dashboard/ because the value of location_filter is overwriten later when looking for the value of is_perf_issue_service.

Updating the logic so that:
 - for catapult try jobs, which has neither is_dashboard nor is_perf_issue_service, it should has both dasboard/ and perf_issue_service/ as exclusive path.
 - for dashboard try job, which has is_dasboard, should add perf_issue_servie/ as exclusive path.
 - for perf_issue_service try job, which has is_perf_issue_service, should add dashboard/ as exclude path.

Bug: chromium:1439636
Change-Id: I2dd53081b95c79cc3b2d2f764041624ec7fbfbf1
Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/4568656
Reviewed-by: Funing Wang <funing@google.com>
Commit-Queue: Wenbin Zhang <wenbinzhang@google.com>
2 files changed
tree: 0701dabe9f3b701e6c07fe97858d1a3b5668268b
  1. bin/
  2. catapult_build/
  3. common/
  4. dashboard/
  5. dependency_manager/
  6. devil/
  7. docs/
  8. experimental/
  9. hooks/
  10. infra/
  11. netlog_viewer/
  12. perf_issue_service/
  13. skia_bridge/
  14. systrace/
  15. telemetry/
  16. third_party/
  17. trace_processor/
  18. tracing/
  19. web_page_replay_go/
  20. .eslintignore
  21. .eslintrc
  22. .gcloudignore
  23. .gitignore
  24. .vpython
  25. .vpython3
  26. AUTHORS
  27. BUILD.gn
  28. codereview.settings
  29. CONTRIBUTING.md
  30. DIR_METADATA
  31. generate_telemetry_build.py
  32. LICENSE
  33. navbar.md
  34. OWNERS
  35. PRESUBMIT.py
  36. pylintrc
  37. README.md
  38. WATCHLISTS
README.md

Catapult

Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:

These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.

Contributing

Please see our contributor's guide