Difference between revisions of "Create a Globalyzer only project"
(→Name the Project) |
(→Validate) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 25: | Line 25: | ||
Select ''Next'' |
Select ''Next'' |
||
| + | =Accessors = |
||
| − | = Provide User and Team Access = |
||
[[File:GzAccessors.png|center|600px]] |
[[File:GzAccessors.png|center|600px]] |
||
| Line 33: | Line 33: | ||
Select ''Next'' |
Select ''Next'' |
||
| − | = |
+ | = Globalyzer Settings = |
| Line 62: | Line 62: | ||
Select '''Next'' to validate the Globalyzer configuration: |
Select '''Next'' to validate the Globalyzer configuration: |
||
| + | |||
| + | =Validate Globalyzer Configuration= |
||
[[File:GzValidate.png|center|600px]] |
[[File:GzValidate.png|center|600px]] |
||
Latest revision as of 14:36, 29 October 2025
Contents
Data Source Settings
For this example, we are using the GitHub repository. Other Data Source types are similar. Enter the credentials, the repository URL, and the branch that is being used for the project.
If the repository has branches that merge into the project branch, this can be specified.
Click Next
Project Name
The values on this page are initially filled in based on the repository and can be changed at creation or later while editing.
- Set the Group Name. Often, this is the same as the Company Name that Command Center was installed with. But it can be almost anything. There is a restriction that it must be the same case. For example, if the Group Name for other projects is ACME (all caps), then another project cannot be created with a group name of 'acme' or 'Acme'.
- Set the Project Name. Project name must be one word and cannot contain any of the following characters: < > : " * / | ? . % --
- Set the Module Name. This is defaulted to the branch that the project is using.
- Tags - tags can be selected from a drop-down list of already created tags or new ones can be created by selecting the plus sign. Projects can have a number of tags associated with them.
- Select the Project Run Type. A project can be a Globalyzer project, a Localyzer project or both. By default these are unselected. The user cannot select Next until at least one option is selected.
Select Next
Accessors
Select the Users and Teams that will have access to this project. Also verify the users that will receive email notifications for this project.
Select Next
Globalyzer Settings
Both of the prompts on this page depend on files in the Settings -> System Files -> Globalyzer Lite Files and Custom Scripts. If these are not set up then use the default settings.
Script to Generate Globalyzer reports.
Apply ChatGPT Prediction to Globalyzer Reports. Enables and disables the automatic prediction of ChatGPT to all issues detected by Globalyzer.
ChatGPT Token. Token used by ChatGPT when leveraging ChatGPT predictions.
For details on using ChatGPT with Globalyzer see Globalyzer and ChatGPT
Project Definition File Where in the repository is the Globalyzer Lite Project Definition file?
For example, if your repository is
https://github.com/Acme/MyProject
and the Lite Project Definition File is in the lingoport folder and called PDF.xml
then the entry for Project Definition File would be:
/lingoport/PDF.xml
If the path or the file is incorrect or the file is not a Globalyzer Lite Project Definition file, then the error will be: Invalid lite file. The file needs to be correct before moving forward.
Select 'Next to validate the Globalyzer configuration:
Validate Globalyzer Configuration
Click Create to finalize the project creation. This will display the new project. Click Analyze for the first results.
