commit | f1eeae7a42da5ecbcf88aaf61e70f35f073de3c1 | [log] [tgz] |
---|---|---|
author | Julio Hurtado <juahurta@google.com> | Mon Aug 05 18:09:00 2024 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 05 18:15:05 2024 |
tree | 810781eb30503dee73cbb5b3f0a29eb930761609 | |
parent | 66f7e013ed55106bd0e32af6e4d0c13a4fc1098b [diff] |
susch: manually scale susch gae app BUG=b:338128764 TEST=None Change-Id: I9c631260217a67e1fd8b4987a966c19c4e5804aa Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/suite_scheduler/+/5762515 Reviewed-by: Derek Beckett <dbeckett@chromium.org> Reviewed-by: Varun Srivastav <varunsrivastav@google.com> Commit-Queue: Chris DeLaGarza <cdelagarza@google.com> Tested-by: Julio Hurtado <juahurta@google.com> Commit-Queue: Derek Beckett <dbeckett@chromium.org> Auto-Submit: Julio Hurtado <juahurta@google.com> Reviewed-by: Chris DeLaGarza <cdelagarza@google.com>
suite-scheduler is an AppEngine Standard Python Environment V1 application. You need the Google Cloud SDK's AppEngine Python component to develop and deploy this application:
gcloud auth login <username>@google.com
./install_gcp_reqs
Suite-scheduler development must be done in the standard Chrome OS source checkout but entirely outside the Chrome OS chroot environment.
suite-scheduler uses depot_tools/vpython
to provide a stable environment for development and release.
First, make sure you have depot_tools installed and stored within your $PATH
Then, to (re)initialize developer environment, run
bin/setup_environment
For testing changes beyond to the configs/
directory, and for deploying suite-scheduler, you must also obtain certain service credentials used by suite-scheduler.
bin/setup_environment --load-creds
If you get failures when trying to download credentials,
gcloud auth list
.Changes must be validated with the full test suite:
bin/run_tests bin/run_tests --debug # More verbose
These tests include some integration tests that can take over 5 minutes to run.
** WARNING: suite-scheduler unittests do not currently run in presubmit. You MUST ensure that unit-tests pass locally for your change. **
Changes to suite-scheduler configs are made in config-internal, as of 2020. Detailed instructions on adding/editing config files can be found at go/ss-configs.
There are two instances of suite-scheduler:
Detailed deployment instructions can be found at go/suite-scheduler#deployment.