...
Project name / sub-project name
Last update - a timestamp per UTC of last data import
Action icon to launch a data load for a specific data source per a specific project (NOTE: only if permissions allow)
A status of last execution - can be "ok", "error" or "in progress"
Update time - in seconds, a duration of last data load
Result - a textual summary of data entries loaded within last launch
Source - a url to an instance of a tool from where data had been loaded.
...
Start Data load
User can start data load for a project from the Administration page.
Open Perf Administration page, Projects tab
Clicks on icon in the “Data load” column
Select option:
Option | Description |
|---|---|
Incremental update only this data source subject | the latest data (after previous data load) is loaded for the selected data source subject (for example, repository in GIT) of the particular project |
Incremental update only this data source (all subjects) | the latest data is loaded for the selected data source of the particular project |
Incremental update for all data source within this project | the latest data is loaded for the all configured data sources of this particular project. |
Full update only this data source subject | all the data is loaded from scratch for the selected data source subject (for example, repository in GIT) of the particular project |
Full update only this data source (all subjects) | all the data is loaded from scratch for the selected data source of the particular project |
Full update for all data sources within this project | all the data is loaded from scratch for the all configured data sources og this particular project. |
...
Users and permissions
| Note |
|---|
This view is available only for users with Administrator permissions. |
...
This mechanism (if enabled) may work in two different ways:
Loading repositories into memory.
Warning This option may cause a side effect. Some repositories are so large they can’t fit into memory. It increases the risk of out-of-memory (OOM) failure. The problem is completely resolved if repositories are stored on disk. It is also cheaper.
Loading and storing repositories to HDD (it's a little slower, however more reliable and cheaper solution comparing to in-memory storage).
Otherwise, if git clone option is disabled, git API data load will be started.
...
There are several ways to enable and configure the feature:
To apply git cloning exclusively to specific data sources just type their id`s (comma separated) into whitelist field. Use '*' for enabling feature for all data sources across the application.
If you want to exclude some data sources, type theirs id`s into blacklist (some of data sources may contain 100k+ commits and repositories and size of repo may be too large).
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|