Each rule has a name specified by the name attribute of type string. The name must be a syntactically valid target name, as specified above. In some cases, the name is somewhat arbitrary, and more interesting are the names of the files generated by the rule, and this applies to genrules. For more information, see General rules: genrule. In other cases, the name is important: for example, for rules *_binary and *_test, the name of the rule determines the name of the executable generated by the build. ctx.workspace_name do not give the right answers. For example, when I print(«`%s`-> `%s`», (ctx.label.workspace_root, ctx.workspace_name)), I get results like: When it comes to retrieving the workspace name, it seems to be suboptimal, but it also seems to work: If you use an established workspace as a template, a warning message appears asking you to select one of the following options: Note: After enabling a workspace for Data Grid, you can no longer reset it to SQL through the Relativity frontend. If you need to unactivate the data grid, you must contact Relativity Support. Note: All groups that are part of a model workspace are also part of the client domain workspace. These non-client domain groups must be removed to prevent the client domain administrator from displaying information about non-client domain users and groups.

I am not sure that this selection is necessary. The main cause is that Bazel evaluates errors in workspace files and reports them when they don`t. On the Workspace Details tab, Relativity displays read-only workspace fields, historical information, the Relativity Utilities console, production constraints, and the workspace Administrators Group field. You can update the Production Constraints field when you edit a workspace. See Adding and Modifying Production Constraints. For technical and legal reasons, you can`t edit the legal entity information for an existing billing or reseller account. Instead, you`ll need to set up a new account. See below for possible options or alternatives. All of the following non-document objects in the template are copied to the new workspace: When you delete a workspace, the following events occur in relativity: Note: It is recommended that you select an empty workspace without documents as a template to avoid possible errors when cleaning up all references. Relative labels cannot be used to refer to destinations in other packages.

The repository ID and package name must always be specified in this case. For example, the source tree contains both the my/app package and the my/app/testdata package (that is, each of these two directories has its own BUILD file). This last package contains a file named testdepot.zip. Here are two ways (one wrong, one correct) to reference this file in //my/app:BUILD: Unfortunately, there are scenarios where directory labels must be used. For example, if the testdata directory contains files whose names do not match the label syntax, explicitly enumerating the files or using the glob() function will result in an invalid label error. You should use directory labels in this case, but be aware of the associated risk of erroneous reconstructions described above. A package is defined as a directory that contains a file named BUILD or BUILD.bazel that is located under the top-level directory in the workspace. A package contains all the files in its directory, as well as all the subdirectories it contains, except those that themselves contain a BUILD file. You can use a placement attribute and then use it ctx.workspace_name in your implementation.

Note: Credentials for Aspera, Aspera Node, Azure, and Azure File System can only be specified when creating new workspaces. They cannot be added by editing the details of the existing workspace. The srcs attribute present in many rules is of the «label list» type; Its value, if any, is a list of labels, each of which is the name of a target that is an entry in that rule. At the workspace level, you can also define views, layouts, fields, and choices. These relativity features streamline workflows and simplify the processes of organizing and categorizing content. Views support filtering by lists of items, while layouts, fields, and choices are used to categorize documents. Note: You must have delete permissions on the workspace object to delete a workspace. Retrieving workspaces does not occur immediately after you click Get Workspace, it may take 24 hours to 5 days to resume operations in that workspace. The user who submitted the pull request receives an email notification when the workspace recovery is complete. Directories that contain a file named WORKSPACE are considered the root of a workspace. Therefore, Bazel ignores all directory trees in a workspace rooted in a subdirectory that contains a WORKSPACE file (because they form a different workspace). Each rule has a set of attributes.

The attributes applicable to a particular rule, as well as the meaning and semantics of each attribute, are a function of the rule class. For a list of rules and corresponding attributes, see the Generation Encyclopedia. Each attribute has a name and a type. Some of the most common types that an attribute can have are Integer, Label, List of Labels, String, List of Strings, Output Label, List of Output Labels. Not all attributes need to be specified in every rule. The attributes thus form a dictionary of keys (names) with optional typed values. The second part of the label is the unqualified package name my/app/main, the path to the package relative to the repository root. Together, the repository name and the unqualified package name make up the fully qualified package name @myrepo//my/app/main. If the label refers to the same packaging in which it is used, the name of the package (and possibly the colon) may be omitted. For example, in @myrepo//my/app/main, this label can be written in one of the following ways: Package names cannot contain the // substring or end with a forward slash.

The first part of the label is the repository name @myrepo//. In the typical case where a label points to the same repository from which it is used, the repository identifier can be abbreviated to ://. If it`s not ausreicht@myrepo to update the company information on your invoices, the best way to update your legal entity is to transfer your Google subscription to a Google partner. The partner can then set up a new billing account for you using your new legal entity information. The workspace rules provided with Bazel are documented in the Workspace Rules section of the Build Encyclopedia and in the rules documentation of the built-in Starlark repository.