Lines Matching +full:python +full:- +full:script +full:- +full:sync +full:- +full:check

11 The config payloads are [Protocol Buffers](https://developers.google.com/protocol-buffers)
21 internal-manifest checkout and should not run these steps.**
31 1. Follow the [Chromium OS Quick Start Guide](http://www.chromium.org/chromium-os/quick-start-guide)
39 1. Run the following command to sync your `$PROGRAM` and `$PROJECT` from within your
43    ./setup_project.sh --program=$PROGRAM --project=$PROJECT
48    manifest, and finally doing a full chromiumos sync.
56 about private partner-specific projects. Infrastructure now exists to create
57 a project-specific buildspec from a local_manifest.xml file. The following
58 workflow explains how to include said project-specific buildspecs in a public
59 ChromeOS checkout, so that partners can properly sync to a specific ChromeOS
64 … like to sync to, e.g. `full/buildspecs/92/13963.2.0.xml`. You can list available buildspecs by ru…
66 …roject-specific buildspecs are automatically created for enrolled projects for new build versions …
67 …-access/project-buildspec -p 'projects=["{your project}/{your program}"]' -p buildspec={your build…
74 …1. ```(mkdir -p $CHECKOUT && cd $CHECKOUT && repo init -u gs://chromiumos-manifest-versions/$BUILD…
75 …1. ```./setup_project.sh --checkout=$CHECKOUT --program=$PROGRAM --project=$PROJECT --buildspec=$B…
77 …1. ```cd $CHECKOUT && repo sync --force-sync -j12 --nmu``` (`--nmu` is a temporary workaround to a…
79 Run `./setup_project.sh -h` for a full list of options/arguments, e.g. `--chipset`, `--all_projects…
85 …-buildspec build via bb add, they need to be added to [cria/project-chromeos-partner-access](https…
87 …ec creation by adding them to the `project_buildspecs` property of `manifest-doctor` ([example](cr…
88 …miumos checkout, run ```./src/config/sbin/create_partner_repo --run createprogrambuckets --program…
92 * [go/per-project-buildspecs](http://go/per-project-buildspecs)
93 * [go/cros-partner-buildspec-sync](http://go/cros-partner-buildspec-sync)
97 **As of 6/8/2020, profiles have not been set up for all projects. Please check with your Google rep…
103 (cr) $ setup_board --board=$PROGRAM --profile=$PROJECT
109 (cr)  ~/trunk/src/scripts $ ./build_packages --board=$PROGRAM
117 - The above profiles work by setting Portage `USE` flags which affect the
125 - The `project_all` `USE` flag is a convenience to use all projects.
167 `gen_config` script (added to the `PATH` above). An example session updating
185 …AM/$PROJECT/generated/project/sw_build_config/platform/chromeos-config/generated/project-config.js…
188 [encoded as JSON](https://developers.google.com/protocol-buffers/docs/proto3#json).
190 …-config.json` is the config in the [legacy YAML schema](https://chromium.git.corp.google.com/chrom…
191 and is present for backwards-compatibility.
193 Before uploading the changes for review you should check to see if your
195 script from within your project's root directory:
214 [gerrit](https://chrome-internal-review.googlesource.com/). The exact URL
220 …iew](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/contributing.md#Going-through-review)
232 build are mirrored to per-project Google Storage buckets. The Google Storage
238 (e.g. add a field), edit the `.proto` file and then run the `generate.sh` script
241 See the [proto3 Language Guide](https://developers.google.com/protocol-buffers/docs/proto3)
250 Constraints look and behave similar to Python unit tests, but are passed a
252 …AD/payload_utils/checker/common_checks/) directory. Constraints can also be program-specific; these
254 see the [Galaxy](https://chrome-internal.googlesource.com/chromeos/program/galaxy/+/HEAD/checks/)
285 - `proto/`: Protobuf definitions for hardware configuration,
289 - `util/`: Starlark utilities for use in program and project repos. Some
294 - `test/`: A fake program and project. Useful to demonstrate the use of the
297 - `bin/`: Tools needed to work in the configuration ecosystem, see the [above
298 section](#Adding-Utilities-to-Your) on adding these tools to your `PATH`.
300 - `go/`: Golang proto bindings. Used by platform code.
302 - `python/`: Python proto bindings. Used by platform code.
307 - `infra/`, `recipes/`: Needed to roll proto definitions into
308 [Recipes](https://chromium.googlesource.com/infra/luci/recipes-py) repos.
310 - `payload_utils/`: Utilities for working on configuration payloads, e.g. CQ
313 - `presubmit/`: Common files and libraries for program and project repo
316 - `sbin/`:  Tools admins use to create and manage programs and projects.
324 - `config.star`: The main Starlark file to generate a program or project's
326 [Making Configuration Changes for your Project](#Making-Configuration-Changes-for-your-Project)
328 - `generated/`: Generated configuration payloads.
330 - `sw_build_config/`: Files for configuring software on the project's build.
331 Contains manually-edited and generated files.
333 - `public_sw_build_config/`: A filtered version of `sw_build_config`, for use
336 - `local_manifest.xml`: Local manifest for working on the project. See
337 [Project Setup for Partners](#Project-Setup-for-Partners)
339 - `config/`: Symlink to the `chromiumos/config` repo, for importing Starlark
342 - `program/`: Symlink from a project repo to the corresponding program repo, for
343 importing program-level Starlark functions.
345 - `PRESUBMIT.py`, `PRESUBMIT.cfg`: Presubmit configuration files. Shared across
366 these changes locally, setting commit messages, wiring up Cq-Depends, and
375 A wrapper script,
385   --cl https://chrome-internal-review.googlesource.com/c/chromeos/program/galaxy/+/3095418 \
386   --regex src/program src/project \
387   --reviewers reviewer1@chromium.org reviewer2@google.com \
388   --ccs author@google.com \
389   --hashtag regen-audio-configs \
390   --message "Regenerate audio configs per changes at program level.
418 repo start --all fixbuggyvalue
421 find src/project -name config.star -exec sed -i 's/buggyvalue/goodvalue/' {} \;
424 repo forall -r src/project -c 'git commit -a -m"
432 repo upload --ht=fixbuggyvalue --re=reviewer@google.com
438 gerrit label-cq `gerrit --raw search "owner:me hashtag:fixbuggyvalue"` 1
445 for cl in `gerrit -i --raw search "owner:me status:open hashtag:fixit"`; do