Jonas Termansen
67a7eb63e5
The devtools cipd packages are now automatically built in the secure release infrastructure and humans are no longer able to directly upload the cipd packages. Cherry-picks to the release branches are handled by specially triggering the secure builder. Bug: b/297020298 Change-Id: I8d587cf787b85abea1762c7f302b261298adf83d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/323640 Reviewed-by: William Hesse <whesse@google.com> Commit-Queue: Jonas Termansen <sortie@google.com>
15 lines
792 B
Markdown
15 lines
792 B
Markdown
This folder contains a pre-built Dart DevTools instance which can be served
|
|
as a web application, as well as the package:devtools_server and package:devtools_shared
|
|
packages from the same revision, used to host and launch DevTools from a Dart process.
|
|
|
|
To build DevTools and update the CIPD resources, do the following:
|
|
|
|
- Commits on devtools master are automatically built and packaged in CIPD.
|
|
If a cherry-pick must be rolled into DEPS, then follow
|
|
go/dart-engprod/devtools.md to manually trigger a secure devtools cipd build.
|
|
- Update DEPS to point to the newly updated DevTools by providing "revision:<revision>"
|
|
as the version entry for "third_party/devtools"
|
|
|
|
DevTools CIPD packages are located at
|
|
https://chrome-infra-packages.appspot.com/p/dart/third_party/flutter/devtools/+/.
|