Package com.google.devtools.build.lib.runtime.proto

Interface CommandLineOuterClass.CommandLineOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
CommandLineOuterClass.CommandLine, CommandLineOuterClass.CommandLine.Builder
Enclosing class:
CommandLineOuterClass
public static interface CommandLineOuterClass.CommandLineOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Details

    • getCommandLineLabel

      String getCommandLineLabel()
       A title for this command line value, to differentiate it from others.
 In particular, a single invocation may wish to report both the literal and
 canonical command lines, and this label would be used to differentiate
 between both versions. This is a string for flexibility.
      string command_line_label = 1;
      Returns:
      The commandLineLabel.

    • getCommandLineLabelBytes

      com.google.protobuf.ByteString getCommandLineLabelBytes()
       A title for this command line value, to differentiate it from others.
 In particular, a single invocation may wish to report both the literal and
 canonical command lines, and this label would be used to differentiate
 between both versions. This is a string for flexibility.
      string command_line_label = 1;
      Returns:
      The bytes for commandLineLabel.

    • getSectionsList

      List<CommandLineOuterClass.CommandLineSection> getSectionsList()
       A Bazel command line is made of distinct parts. For example,
 `bazel --nomaster_bazelrc test --nocache_test_results //foo:aTest`
 has the executable "bazel", a startup flag, a command "test", a command
 flag, and a test target. There could be many more flags and targets, or
 none (`bazel info` for example), but the basic structure is there. The
 command line should be broken down into these logical sections here.
      repeated .command_line.CommandLineSection sections = 2;

    • getSections

      CommandLineOuterClass.CommandLineSection getSections(int index)
       A Bazel command line is made of distinct parts. For example,
 `bazel --nomaster_bazelrc test --nocache_test_results //foo:aTest`
 has the executable "bazel", a startup flag, a command "test", a command
 flag, and a test target. There could be many more flags and targets, or
 none (`bazel info` for example), but the basic structure is there. The
 command line should be broken down into these logical sections here.
      repeated .command_line.CommandLineSection sections = 2;

    • getSectionsCount

      int getSectionsCount()
       A Bazel command line is made of distinct parts. For example,
 `bazel --nomaster_bazelrc test --nocache_test_results //foo:aTest`
 has the executable "bazel", a startup flag, a command "test", a command
 flag, and a test target. There could be many more flags and targets, or
 none (`bazel info` for example), but the basic structure is there. The
 command line should be broken down into these logical sections here.
      repeated .command_line.CommandLineSection sections = 2;

    • getSectionsOrBuilderList

      List<? extends CommandLineOuterClass.CommandLineSectionOrBuilder> getSectionsOrBuilderList()
       A Bazel command line is made of distinct parts. For example,
 `bazel --nomaster_bazelrc test --nocache_test_results //foo:aTest`
 has the executable "bazel", a startup flag, a command "test", a command
 flag, and a test target. There could be many more flags and targets, or
 none (`bazel info` for example), but the basic structure is there. The
 command line should be broken down into these logical sections here.
      repeated .command_line.CommandLineSection sections = 2;

    • getSectionsOrBuilder

      CommandLineOuterClass.CommandLineSectionOrBuilder getSectionsOrBuilder(int index)
       A Bazel command line is made of distinct parts. For example,
 `bazel --nomaster_bazelrc test --nocache_test_results //foo:aTest`
 has the executable "bazel", a startup flag, a command "test", a command
 flag, and a test target. There could be many more flags and targets, or
 none (`bazel info` for example), but the basic structure is there. The
 command line should be broken down into these logical sections here.
      repeated .command_line.CommandLineSection sections = 2;