{"push_id":2607101807,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"2027f715abd05b41ae8bac0c1d2fab97fe49275d","before":"5bcad5f49d0847bbf113571d5f3432ad6f53a2f7","commits":[{"sha":"2027f715abd05b41ae8bac0c1d2fab97fe49275d","author":{"name":"Petr Hosek","email":"28e431f5669ee416eed3c0cf0e57e28af39903b5@google.com"},"message":"Use explicit revision when importing Jiri manifest when possible\n\nWhen triggering a build job, scheduler sends a revision for which the\nbuild was triggered as 'revision' property. However, Jiri was ignoring\nthat property and always imported the manifest from tip-of-tree. This\nmeans that the revision we're actually building might be potentially\ndifferent from the revision we were triggered for.\n\nJiri was recently extended to support specifying import revision.  This\nchange modifies all recipes to always pass the explicit revision to the\nimport command when available. There has also been some cleanup some\nunused arguments to ensure consistency across recipes.\n\nChange-Id: I99bd1843841477c3a5410f0b02aa78154d8c2549","distinct":true,"url":"https://api.github.com/repos/fuchsia-mirror/infra-recipes/commits/2027f715abd05b41ae8bac0c1d2fab97fe49275d"}]}
{"actor":{"display_login":"fuchsia-infra-bot"}}