Use revision instead of build number for TC query.
What does this MR do?
This MR changes the behavior of the TC integration to use the "revision" field to query for builds for certain revisions. Formerly it was using the "build" field which corresponds to the build number in TC, which is configurable, and often can't be easily modified to contain only the revision of the build.
Also there might be more than one VCS in a given project. When querying for revision instead, any build with the matching revision in at least one VCS will be found.
I am unsure if this MR warrants a changelog entry or not. As far as I can tell, it is not breaking existing integrations to TC, as the revision field is always populated if the former (build.vcs.number) would be. It is, however, a user facing change in the strictest sense, because the user might not need to adjust his build numbering scheme anymore.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
Tests added for this feature/bug -
Tested in all supported browsers -
Conforms to the code review guidelines -
Conforms to the merge request performance guidelines -
Conforms to the style guides -
Conforms to the database guides -
Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process. -
Security reports checked/validated by reviewer