Shared indexes

Prepare a file storage

Sharing indexes from the command line requires that you have a file storage that will keep the exported project indexes.

• Make sure that you have a file storage ready, and all members of your team have access to this storage.

Install the upload-local tool

To be able to export and share project indexes, install the upload-local tool:

1. Download the upload-local/<version>/upload-local-<version>.zip artifact from Bintray. We recommend that you get the latest version of the tool.

2. Extract the contents of the .zip file.

   Among the .zip file's content, there's a bin directory. There, you will find an OS-specific startup script that you will need later for generating metadata.

Prepare the IDE for sharing project indexes

1. Create the following directories or remove the contents from the existing ones:

   • <temp>/ide-system
   • <temp>/ide-config
   • <temp>/ide-log

   Note that in different operating systems, the temp directory has a different location.

2. Copy the <IDE home>/bin/idea.properties file to the <temp> directory.

   Rename idea.properties to ide.properties in <temp>.

3. Change the following properties in the <temp>/ide.properties file:

   • idea.system.path=<temp>/ide-system
   • idea.config.path=<temp>/ide-config
   • idea.log.path=<temp>/ide-log

   If you don't have these properties in the file, add them at the end.

4. Set a temporary environment variable to specify the custom IDE properties file. To do so, run the following command:

   set IDEA_PROPERTIES=<temp>\ide.properties

   export IDEA_PROPERTIES=<temp>/ide.properties

Export project indexes

1. Make sure that the <temp>/generate-output directory is empty. If there's no such directory, do not create it as this will be done automatically during the export.

2. Run the IDE with the following command line to export the project indexes to <temp>/generate-output.

   <IDE command-line launcher> dump-shared-index project --output=<temp>/generate-output --tmp=<temp>/temp --project-dir=<path> --project-id=<project-name> --commit=<Git HEAD>

   You can find the script for running RubyMine in the installation directory under bin. To use this script as the command-line launcher, add it to your system PATH as described in Command-line interface.

   Syntax

   rubymine.bat dump-shared-index project --output=<temp>/generate-output --tmp=<temp>/temp --project-dir=<path> --project-id=<project-name> --commit=<Git HEAD>

   Options

   --output=<temp>/generate-output	Output location for the generated shared indexes in the <temp> folder.
   --tmp=<temp>/temp	The temp directory used for the internal needs of the IDE.
   --project-dir=<path>	The path to the project for which you want to export indexes.
   --project-id=<id>	The name of the project.
   --commit=<vcs revision>	The VCS revision identifier (for example, Git commit hash) representing the state of the project for which the shared index is being generated. This is needed to lay out the shared indexes of several VCS revisions in the file storage. This identifier is optional. If it is not specified, it will be set to -.

   By default, RubyMine does not provide a command-line launcher. For information about creating a launcher script for RubyMine, see Command-line interface.

   Syntax

   rubymine dump-shared-index project --output=<temp>/generate-output --tmp=<temp>/temp --project-dir=<path> --project-id=<project-name> --commit=<Git HEAD>

   Options

   --output=<temp>/generate-output	Output location for the generated shared indexes in the <temp> folder.
   --tmp=<temp>/temp	The temp directory used for the internal needs of the IDE.
   --project-dir=<path>	The path to the project for which you want to export indexes.
   --project-id=<id>	The name of the project.
   --commit=<vcs revision>	The VCS revision identifier (for example, Git commit hash) representing the state of the project for which the shared index is being generated. This is needed to lay out the shared indexes of several VCS revisions in the file storage. This identifier is optional. If it is not specified, it will be set to -.

   You can find the script for running RubyMine in the installation directory under bin. To use this script as the command-line launcher, add it to your system PATH as described in Command-line interface.

   Syntax

   rubymine.sh dump-shared-index project --output=<temp>/generate-output --tmp=<temp>/temp --project-dir=<project> --project-id=<project-name> --commit=<Git HEAD>

   Options

   --output=<temp>/generate-output	Output location for the generated shared indexes in the <temp> folder.
   --tmp=<temp>/temp	The temp directory used for the internal needs of the IDE.
   --project-dir=<path>	The path to the project for which you want to export indexes.
   --project-id=<id>	The name of the project.
   --commit=<vcs revision>	The VCS revision identifier (for example, Git commit hash) representing the state of the project for which the shared index is being generated. This is needed to lay out the shared indexes of several VCS revisions in the file storage. This identifier is optional. If it is not specified, it will be set to -.

   The export might take some time. When the process is finished, the following files are placed to <temp>/generate-output:

   • shared-index-project-<name>-<hash>.ijx.xz
   • shared-index-project-<name>-<hash>.metadata.json
   • shared-index-project-<name>-<hash>.sha256

Copy the generated files to a new folder

1. Create a new directory <temp>/indexes and download there all the contents of your remote file storage.

2. Copy the generated files (.ijx.xz, .metadata.json, .sha256) from <temp>/generate-output to a subdirectory of <temp>/indexes.

   This can be any folder, for example <temp>/indexes/project/<project name>/<VCS hash>/<indexes>.

Generate metadata

• Generate auxiliary files used by the IDE to look up for and download shared indexes. To do so, run the upload-local tool with the following command line.

  <upload-local tool> --indexes-dir=<temp>/indexes --url=<file storage root UR>

  Options

  <upload-local tool>	The path to the upload-local tool startup script located in bin in the tool directory.
  --indexes-dir=<dir>	The directory containing all the files available in the file storage, as well as the newly generated shared indexes residing in a suitable location beneath this directory. The tool will generate the missing files and replace existing ones if necessary. After the tool has finished running, all the contents of this directory must be uploaded to the file storage. This will set the new state of the storage.
  --url=<file storage root URL>	The base URL of the file storage root directory. The upload-local tool will substitute the download URL in all the corresponding .json index lists.

  Example

  /Users/User/Desktop/upload-local-1.0.3/bin/upload-local --indexes-dir=/var/folders/dr/xxx_x00x0x0_x0xx000xx000000xx/T/indexes --url=https://my-file-storage.com/intellij-indexes

Upload the index files to your file storage

• Upload all the files from <temp>/indexes to the file storage as is.

  If there are already uploaded index files in the storage, update them.

1. In the project directory, create a new file intellij.yaml and add the following code:

   sharedIndex: project: - url: <feed URL>

   Replace <feed URL> with the URL of your file storage in the following format: <file storage root URL>/project/<project-id>.

2. In the Settings/Preferences dialog Ctrl+Alt+S, select Tools | Shared Indexes.

3. From the Project indexes list, select how you want to download shared indexes from the storage.

   Select Download automatically to allow RubyMine to download the JDK indexes silently whenever they are needed or select Ask before download if you prefer to confirm every download manually.

   

4. Apply the changes and close the dialog.

Project indexes will be downloaded to index/shared_indexes in the IDE system directory.