Run/debug configuration templatesĪll run/debug configurations are based on templates, which implement the startup logic, define the list of parameters and their default values. For run configurations to make their way to a shared repository, you have to check them in like other versioned files. Turning on the Store as project file option does not submit anything to the VCS for you. If you use Git for your project, you can share. idea/runConfigurations subfolder will be ignored, too. idea directory is added to VCS ignored files, the. If compatibility with DataGrip 2019.3 and earlier is required, store the file in the default location. Select the run configuration you want to share, enable the Store as project file option, and specify the location where the configuration file will be stored. With legacy projects, you can only share all configurations at once by adding the. ipr-based projects do not support individual run configurations. This saves a lot of time as run configurations sometimes get sophisticated, and keeping them in sync manually would be tedious and error-prone. The same mechanism can also be used when you want to send your configuration as a file to someone else. If you are working in a team, you might want to share your run configurations so that your teammates could run the application using the same configuration or enable them to remotely attach to the process you are running.įor these purposes, DataGrip provides a mechanism to store your run configurations as project files and share them through VCS. To run the configuration right away, click Run. You can either run the configuration right away, or save the configuration to run it later.Ĭlick OK to save the run configuration for later and close the dialog. In the Before launch section, define whether you want to perform any specific actions before launching the application, for example, launch an external tool or disconnect from a data source. Select Allow multiple instances if you want to allow multiple instances of the configuration to run at the same time. If a script contains schema switching, you will see a warning ( ).įor more information about settings of the Database Script configuration type, refer to Database script. To add files, click the Add button ( ) and navigate to files that you want to run. Script files: SQL files that you want to run. Script text: script that you want to run. If you select a data source as a target, DataGrip displays a schema in which the script will be run. Target data source / schema: databases or schemas against which you want to run your database scripts. In the Run/Debug Configurations dialog, click the Add New Configuration icon ( ) and select Database Script. Alternatively, press Alt+Shift+F10, then 0. For other templates, refer to List of run/debug configurations. This procedure describes the steps to create a run/debug configuration using the Database Script template. Create a run/debug configuration from a template The list of available templates varies depending on the installed and enabled plugins. Select a temporary configuration in the run configuration switcher, click /, and select Save Configuration.Īlternatively, select a temporary configuration in the Run/debug configurations dialog and click on the toolbar.ĭataGrip provides run/debug configuration templates for different languages, tools, and frameworks. Save a temporary configuration as permanent Save a temporary run/debug configuration as permanent.Ĭreate from a template or copy an existing configuration. Create permanent run/debug configurationsĭataGrip provides the following ways to create a permanent run/debug configuration: If necessary, you can increase this limit in Settings | Advanced Settings | Run/Debug | Temporary configurations limit. The older ones are automatically deleted when new ones are added. The maximum number of temporary configurations is 5. Permanent configurations have opaque icons while the icons of temporary configurations are semi-transparent. So whenever you run/debug or test your code, DataGrip either uses an existing permanent run/debug configuration or creates a new temporary one. Permanent configurations remain as part of your project until you remove them. Permanent - created explicitly from a template or by saving a temporary configuration. To call the context menu, right-click an object or an area. Temporary - created every time you select Run from the context menu. There are two types of run configurations: Each configuration is a named set of startup properties that define what to execute and what parameters and environment should be used. DataGrip uses run/debug configurations to run, debug, and test your code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |