Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Sign in
Toggle navigation
F
Front-End
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
abdullh.alsoleman
Front-End
Commits
11a363b1
Commit
11a363b1
authored
Feb 13, 2016
by
Eric Seidel
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add more instructions on how to edit a recipe.
@abarth
parent
8db6f5b1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
0 deletions
+6
-0
README.md
infra/README.md
+6
-0
No files found.
infra/README.md
View file @
11a363b1
...
...
@@ -27,6 +27,12 @@ Recipes are just python. They are
[
documented
](
https://github.com/luci/recipes-py/blob/master/doc/user_guide.md
)
by the
[
luci/recipes-py github project
](
https://github.com/luci/recipes-py
)
.
The typical cyle for editing a recipe is:
1.
Make your edits.
2.
Run
`build/slave/recipes.py train simulation_test flutter`
to update expected files (remove the flutter if you need to do a global update).
3.
Run
`build/slave/recipes.py run flutter/flutter`
(or flutter/engine) if something was strange during training and you need to run it locally.
4.
Upload the patch (
`git commit`
,
`git cl upload`
) and send it to someone in the
`recipes/flutter/OWNERS`
file for review.
Most of the functionality for recipes comes from recipe_modules, which are
unfortunately spread to many separate repositories. The easiest way to find
documentation on how to use modules is to
[
get a full checkout of chromium's
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment