aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/runtime/commands
Commit message (Collapse)AuthorAge
...
* Change most calls to BlazeRuntime.getReporter() to use CommandEnvironment.Gravatar Ulf Adams2015-09-16
| | | | | -- MOS_MIGRATED_REVID=103175472
* Introduce CommandEnvironment and pass it instead of BlazeRuntime.Gravatar Ulf Adams2015-09-15
| | | | | | | | The very long term plan is to make BlazeRuntime immutable, so that we can run multiple commands in the same server. -- MOS_MIGRATED_REVID=103080946
* Allow canonicalize-flags to run for any command.Gravatar Ulf Adams2015-09-08
| | | | | -- MOS_MIGRATED_REVID=102483838
* Code cleanupGravatar Laurent Le Brun2015-09-03
| | | | | -- MOS_MIGRATED_REVID=102239051
* Collect Skylark profile info and create HTML statistics when --html_details ↵Gravatar Googler2015-09-02
| | | | | | | given -- MOS_MIGRATED_REVID=102046602
* Drop the baseline artifact output group.Gravatar Ulf Adams2015-08-31
| | | | | | | | | | The baseline artifacts are part of the instrumented files provider now, and are strongly tied to the collect_code_coverage flag. It seems to be simpler to collect them explicitly in the BuildView (which already collects them for post-processing), than to rely on the output group selection. -- MOS_MIGRATED_REVID=101926341
* Fixed bug where blaze run with the --color=no flag was still printing out in ↵Gravatar Shreya Bhattarai2015-08-04
| | | | | | | | | color when the build fails. Includes fix for problems causing the original slowdown to blaze query -- MOS_MIGRATED_REVID=99755414
* Rollback of commit 2e7a5b47979b2679208a97a65df265be953eb595.Gravatar Han-Wen Nienhuys2015-08-04
| | | | | | | | | *** Reason for rollback *** Query performance regression. -- MOS_MIGRATED_REVID=99560234
* Add "warm" starting to mobile-install.Gravatar Googler2015-08-04
| | | | | | | | | | | | | | | | | | This introduces a new way to stop applications when deploying incremental changes that saves the current app state for the next run. This allows things like the back stack, and View/Fragment/Activity saved state to be restored when the app next launches, making it easier to quickly iterate on code changes. It adds a "--start" flag to mobile-install that replaces "--start_app". --start accepts an argument describing the mode: no, cold, or warm. "no" is now the equivalent of "--nostart_app", "cold" is the equivalent of "--start_app", and "warm" is the new start mode. Note that this is only useful with incremental installs, as Android clears out any previously saved state when an APK is replaced. -- MOS_MIGRATED_REVID=99508790
* Record the project file used to the master log.Gravatar Googler2015-07-28
| | | | | -- MOS_MIGRATED_REVID=99224654
* Don't choke on Exceptions that have a null error message.Gravatar Han-Wen Nienhuys2015-07-27
| | | | | -- MOS_MIGRATED_REVID=99174214
* Fixed bug where blaze run with the --color=no flag was still printing out in ↵Gravatar Googler2015-07-21
| | | | | | | color when the build fails. -- MOS_MIGRATED_REVID=98736813
* Throw InterruptedException directly if a query is interrupted, instead of ↵Gravatar Janak Ramakrishnan2015-07-10
| | | | | | | | | wrapping it in a QueryException. QueryException should usually indicate a persistent failure, while an InterruptedException is transient. Wrapping the InterruptedException in a QueryException just obfuscates state. -- MOS_MIGRATED_REVID=97815388
* Make globs work in remote repositories.Gravatar Lukacs Berki2015-07-08
| | | | | | | | | | | This involved quite a few changes, mainly changing a bunch of places where we refer to packages by a PathFragment to PackageIdentifier. The only wart is the code in PathPackageLocator: ideally, it would just call into PackageLookupFunction. Unfortunately, it is (through globbing and Parser.include) called from within a Skyframe function, and we don't want to have two eval() calls going on at the same time, so we cannot use that. There is a potential correctness issue there: PathPackageLocator now assumes where external repositories are put and assumes that they are there when it gets control, but my understanding is that the associated RepositoryValue is always evaluated before, so it works out okay. -- MOS_MIGRATED_REVID=97751539
* Rollback of accidentally submitted change.Gravatar Lukacs Berki2015-07-07
| | | | | -- MOS_MIGRATED_REVID=97648982
* Make globs work in remote repositories.Gravatar Lukacs Berki2015-07-07
| | | | | | | | | | | This involved quite a few changes, mainly changing a bunch of places where we refer to packages by a PathFragment to PackageIdentifier. The only wart is the code in PathPackageLocator: ideally, it would just call into PackageLookupFunction. Unfortunately, it is (through globbing and Parser.include) called from within a Skyframe function, and we don't want to have two eval() calls going on at the same time, so we cannot use that. There is a potential correctness issue there: PathPackageLocator now assumes where external repositories are put and assumes that they are there when it gets control, but my understanding is that the associated RepositoryValue is always evaluated before, so it works out okay. -- MOS_MIGRATED_REVID=97647787
* Description redacted.Gravatar Googler2015-06-24
| | | | | -- MOS_MIGRATED_REVID=96703011
* Add dump commandGravatar Kristina Chodorow2015-06-15
| | | | | -- MOS_MIGRATED_REVID=95843033
* Description redacted.Gravatar Lukacs Berki2015-06-10
| | | | | -- MOS_MIGRATED_REVID=95615442
* Add --with_aspect_deps flag to blaze query. This flag should produce ↵Gravatar Lukacs Berki2015-06-05
| | | | | | | | | | | | | additional information about aspect dependencies when --output is set to {xml, proto}. One quirk of this CL is that if BUILD files of direct dependencies are added both under <subinclude> and <load>. Any better ideas are appreciated. As a drive-by fix, if for some reason a package reports the same label as a both subinclude and a Skylark dependency, it will only be reported once in the proto output. RELNOTES[NEW]: added --with_aspect_deps to blaze query, that prints additional information about aspects of target when --output is set to {xml, proto, record}. -- MOS_MIGRATED_REVID=95272042
* Initial checkin of the "mobile-install" command.Gravatar Lukacs Berki2015-05-29
| | | | | | | This was omitted when the bulk of the code was moved in order not to pollute the output of "bazel help" with a useless command, but now it is in the way of testing Android functionality. -- MOS_MIGRATED_REVID=94747309
* Remove 'blaze doc_ext' command.Gravatar Laurent Le Brun2015-05-18
| | | | | | | | | We prefer to focus on the web documentation instead. RELNOTES[INC]: 'blaze doc_ext' command removed. -- MOS_MIGRATED_REVID=93871336
* Fix info-keys help output.Gravatar Thiago Farina2015-05-08
| | | | | | | | | | | | | | Tested on Linux with the following command line: $ bazel help info-keys | sort | uniq -c And compared the output before and after. Fixes #175 -- Change-Id: Ia879796abf6f5b6b5742bfc9574d64fe53a650a3 MOS_MIGRATED_REVID=93127869
* Fix indentation in TestCommand.Gravatar Ulf Adams2015-04-23
| | | | | -- MOS_MIGRATED_REVID=91818123
* Added an help command to dump all options for completionGravatar Damien Martin-Guillerez2015-04-10
| | | | | | | | | | `bazel help completion` dump all options completion pattern for each command, giving hints on the format of the completion residue (e.g., `label`, `path`, `{a,enum}`, ...). This dump can be used to generate completion scripts. -- MOS_MIGRATED_REVID=90743024
* Supply the correct command name to ProjectFileSupport.Gravatar Googler2015-03-31
| | | | | -- MOS_MIGRATED_REVID=89973895
* On-the-fly target pattern resolution in SkyQueryEnvironmentGravatar Mark Schaller2015-03-18
| | | | | | | | | | | | | Moves pattern resolving logic from TargetPatternFunction.Resolver to a top level class. Adds a layer of abstraction to the Resolver implementation enabling it to be backed by either an Environment or a Graph, for use in SkyFunction evaluation or on-the-fly evaluation, respectively. Finally, SkyQueryEnvironment#preloadOrThrow now checks to see if each target pattern exists in the graph, and any that don't will be resolved on-the-fly. -- MOS_MIGRATED_REVID=88861201
* The info command keys now contain the correct product nameGravatar Laurent Le Brun2015-03-10
| | | | | | | | e.g. $ bazel info bazel-bin -- MOS_MIGRATED_REVID=87943280
* Some cleanup changes.Gravatar Ulf Adams2015-03-05
| | | | | -- MOS_MIGRATED_REVID=87821306
* More blaze/bazel name cleanup in help messages.Gravatar Laurent Le Brun2015-03-05
| | | | | -- MOS_MIGRATED_REVID=87728012
* Use the correct product name in Bazel command helpGravatar Laurent Le Brun2015-03-05
| | | | | -- MOS_MIGRATED_REVID=87717872
* HelpCommand: Display the correct name (blaze/bazel).Gravatar Laurent Le Brun2015-03-05
| | | | | -- MOS_MIGRATED_REVID=87712063
* Rename TopLevelArtifactProvider to OutputGroupProvider.Gravatar Lukacs Berki2015-03-05
| | | | | -- MOS_MIGRATED_REVID=87596401
* Get runfiles prefix from the WORKSPACE fileGravatar Kristina Chodorow2015-03-05
| | | | | -- MOS_MIGRATED_REVID=87513766
* Remove --compile_only and --compilation_prerequisites_only; --output_groups ↵Gravatar Lukacs Berki2015-03-04
| | | | | | | can be used in their stead. -- MOS_MIGRATED_REVID=87334648
* Add a SkyQueryEnvironment which runs queries by examining the Skyframe graph.Gravatar Janak Ramakrishnan2015-02-26
| | | | | | | | | This environment eagerly preloads the transitive closure of a specified query "universe", and so may not be as efficient as the standard query for limited-scope queries. It is activated when the universe is specified and ordered results are not requested (since it is currently unable to order results). Tests were modified/added to exercise this environment where deemed interesting. Some ugly hacks were done to add coverage in AbstractQueryTest and friends, because currently even if the full depot is loaded (using //...), individual target patterns most likely won't be present in the graph. A better way to deal with this situation, suggested by felly, is probably to extract target pattern resolution logic to an auxiliary function so that query is able to resolve target patterns without mutating the graph, and then call into the read-only graph with the resolved patterns. That may be done in a follow-up, in which case the "scope" of every query could be //... . -- MOS_MIGRATED_REVID=87257028
* Enforce same behavior for //path/to/package and path/to/packageGravatar Damien Martin-Guillerez2015-02-25
| | | | | | | Having an error message in path/to/package and //path/to/package resolve to //path/to/package:package was a bit strange. -- MOS_MIGRATED_REVID=87171051
* Add back mistakenly deleted interrupt-handling code. Sadly, I can't find a ↵Gravatar Janak Ramakrishnan2015-02-11
| | | | | | | way to test this, because no matter what I do (pipe to a FIFO, run under stdbuf), Blaze doesn't block on outputting there, so I can't interrupt and cause the exception. -- MOS_MIGRATED_REVID=86114736
* Refactor Query code a bit. Get rid of separate SkyframeQueryEnvironment, ↵Gravatar Janak Ramakrishnan2015-02-11
| | | | | | | | | move some utility methods to utility class. The real goal of this CL is to make sure all users of BlazeQueryEnvironment are constructing one through EvaluableBlazeQueryEnvironment#newQueryEnvironment, and not directly. This ensures that alternate implementations of EvaluableBlazeQueryEnvironment will be automatically injected via #newQueryEnvironment. -- MOS_MIGRATED_REVID=86112439
* Extract an EvaluableBlazeQueryEnvironment abstract class from ↵Gravatar Janak Ramakrishnan2015-02-11
| | | | | | | | | | | BlazeQueryEnvironment that exposes an evaluateQuery method, and also implements the non-LabelVisitor-specific parts of BlazeQueryEnvironment, for other implementations' uses. Most of the code is just a straight refactoring of BlazeQueryEnvironment into EvaluableBlazeQueryEnvironment (and BlazeTargetAccessor). Ignoring whitespace changes in [] may be your friend for seeing that it's a straight move. This also allows us to change tests to use QueryCommand.newQueryEnvironment, in preparation for newQueryEnvironment potentially returning a different EvaluableBlazeQueryEnvironment subclass depending on the circumstances. -- MOS_MIGRATED_REVID=86088953
* Add some test coverage for --noorder_results.Gravatar Janak Ramakrishnan2015-02-09
| | | | | -- MOS_MIGRATED_REVID=85902304
* Update from Google.Gravatar Han-Wen Nienhuys2015-02-25
-- MOE_MIGRATED_REVID=85702957
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-05 00:55:14 +0000