Support more filters (API)

[moul]

• artifact_kinds=...
• build_id=...
• build_driver=...
• project_id=...
• mergerequest_author_id=...
• artifact_id=...
• mergerequest_state=...
• build_state=...
• mergerequest_id=...
• with_artifacts=1
• with_mergerequest=1
• artifact_driver=...
• branch_name=...
• artifact_state=...
• job_name=
• merged VS PR VS other
• job_id=

also support the <none> or <other> for enums

[moul]

Starting a list of "interesting" (at least for debug) views:

• all builds with at least 1 artifact, see non-android and non-ios ones: https://yolo.berty.io/?with_artifacts=1
• only a specific build: https://yolo.berty.io/?build_id=https://buildkite.com/berty/berty-open/builds/514
  • as soon as you have a specific build_id, every other flags are ignored
• two specific builds: https://yolo.berty.io/?build_id=https://buildkite.com/berty/berty-open/builds/514&build_id=https://buildkite.com/berty/berty-open/builds/513
  • most of the new flags support having one or more fields
• filter on github project: https://yolo.berty.io/?project_id=https://github.com/berty/berty
• list the build that contains a specific artifact: https://yolo.berty.io/?artifact_id=buildkite_4e55e8d10f2514286c0cb806a8b7636d
• builds on bintray -> https://yolo.berty.io/?build_driver=3
• builds on buildkite -> https://yolo.berty.io/?build_driver=1
• builds on circleci -> https://yolo.berty.io/?build_driver=2 (today: empty)
• builds on github -> https://yolo.berty.io/?build_driver=4 (today: empty)

[moul]

new batch:

• builds for a PR created by a specific author: https://yolo.berty.io/?mergerequest_author_id=https://github.com/n0izn0iz
• only builds that are linked to a PR: https://yolo.berty.io/?with_mergerequest=1
• PR status
  • opened PRs: https://yolo.berty.io/?mergerequest_state=1
  • closed PRs: https://yolo.berty.io/?mergerequest_state=1
• by build states:
  • running: https://yolo.berty.io/?build_state=1
  • failed: https://yolo.berty.io/?build_state=2
  • passed: https://yolo.berty.io/?build_state=3
  • and other ones: https://github.com/berty/yolo/blob/master/api/yolopb.proto#L143-L152
• by PR (can have multiple builds): https://yolo.berty.io/?mergerequest_id=https://github.com/berty/berty/pull/1908

[ekelen]

Is there a reason ?artifact_id=xyz returns the entire build + all of its artifacts? (e.g. curl -u $AUTH "https://yolo.berty.io/api/build-list?artifact_id=buildkite_86a373f48077362ead7782285262b86f" | jq

[moul]

yep, build-list returns builds, and except for the "filter the artifact kinds" which is clearly an "I dont care about other types", filtering by artifact ID, can just be that you know an artifact and want to see the other ones for that build

if you don't want it from the front, feel free to filter it from the front :)

[ekelen]

Filtering by project would be cool, because right now if you have this combination selected, you will also see Chat builds:

Conversely, this selection will only display gombile-ipfs builds:

(Alternatively, for now I can send the project_id (url) as part of the query programmatically even if it will look a bit strange in the URL bar – is there any reason not to do this?)

[moul]

Filtering by project would be cool, because right now if you have this combination selected, you will also see Chat builds:

cannot be done right now, ultra-low priority to address this advanced case, if really you don't like this case, remove the build drivers section from this form until we have "per project" filters :)

[moul]

moved to #2