Revert "Check created_by to ensure cq tags were copied on retry builds"

This reverts commit a2528d57f44f5598788d3dd4d093895cfa77836b.

Reason for revert: This breaks our compilators (eg
and presumably any other build that relies on cq when launched by another builder

Original change's description:
> Check created_by to ensure cq tags were copied on retry builds
> Gerrit appears to be inconsistently copying cq tags on retry builds.
> To ensure we don't get ValueErrors like in:
> This will additionally check that the created_by starts with project
> to ensure the cq tags that protect are actually there.
> Downstream chromiumos CL:
> Downstream build CL:
> Recipe-Nontrivial-Roll: chromiumos
> Bug: 1382577
> Change-Id: I3d40b4931bc046f6469ebee2365bcf41fc875634
> Reviewed-on:
> Reviewed-by: Yiwei Zhang <>
> Commit-Queue: Struan Shrimpton <>

Bug: 1382577
Change-Id: I9aa00934b1b2590da7b496b314821a9792f5b89e
Reviewed-by: Yiwei Zhang <>
Bot-Commit: Rubber Stamper <>
2 files changed
tree: 18ec0f959857aea9c1619af07fcdfcff9dc831a3
  1. doc/
  2. infra/
  3. misc/
  4. recipe_engine/
  5. recipe_modules/
  6. recipe_proto/
  7. recipes/
  8. unittests/
  9. .gitattributes
  10. .gitignore
  11. .style.yapf
  12. .vpython
  13. .vpython3
  14. .vpython3_dev
  16. codereview.settings
  19. OWNERS
  23. recipe.warnings


Recipes are a domain-specific language (embedded in Python) for specifying sequences of subprocess calls in a cross-platform and testable way.

They allow writing build flows which integrate with the rest of LUCI.

Documentation for the recipe engine (including this file!). Take a look at the user guide for some hints on how to get started. See the implementation details doc for more detailed implementation information about the recipe engine.


  • Sign the Google CLA.
  • Make sure your and are configured in git config.

Run the following to setup the code review tool and create your first review:

# Get `depot_tools` in $PATH if you don't have it
git clone $HOME/src/depot_tools
export PATH="$PATH:$HOME/src/depot_tools"

# Check out the recipe engine repo
git clone $HOME/src/recipes-py

# make your change
cd $HOME/src/recipes-py
git new-branch cool_feature
# hack hack
git commit -a -m "This is awesome"

# This will ask for your Google Account credentials.
git cl upload -s -r
# Wait for approval over email.
# Click "Submit to CQ" button or ask reviewer to do it for you.
# Wait for the change to be tested and landed automatically.

Use git cl help and git cl help <cmd> for more details.