Right now we have many different properties which are involved with recipes that receive a patchset:
* patch_project
* patchset
* patch_storage
* issue
* patch_gerrit_url
* patch_git_url
* patch_issue
* patch_project
* patch_ref
* patch_set
And maybe others? This is wayyy too many properties. All of these cases could conceptually be reduced to a single property "patch_url", which the recipe would interpret and be able to apply appropriately (even if it was just a step that expanded the url into these existing properties, at least the API to the recipe would be sane).
I think we're at the point where such a cleanup would be possible, especially after we have issue 662654 resolved.
Comment 1 by no...@chromium.org
, Feb 21 2017