-
Notifications
You must be signed in to change notification settings - Fork 1
Running the Merganser
Moein Owhadi-Kareshk edited this page Dec 4, 2018
·
3 revisions
You can run Merganser with all available options (store all available information) by executing the following command:
./runAll <repository_list_name>Where <repository_list_name> is the list of repositories, stored in a *.txt file in ./working_dir/repository_list (this path is REPOSITORY_LIST_PATH which is set in config.py). However, if you want to customize the execution by avoiding extraction of some tables, you should run:
python3 main.py <parameters>Using the following parameters:
| Parameter | Description |
|---|---|
-r or --repository-list
|
The list of GitHub repositories |
-c or --compile
|
If set, the merged code (if successfully merged using the given tool) will be compiled |
-t or --test
|
If set, the repository's test suite will be run after a successful merge |
-cf or --conflicting-file
|
If set, the Conflicting_File table will be populated |
-cr or --conflicting-region
|
If set, the Conflicting_Region table will be populated |
-pr or --pull-request
|
If set, pull requests are detected |
-rc or --replay-compare
|
If set, the replays and merge commits are compared |
-cd or --commit-details
|
If set, the information of all commits that are involved in merge scenarios are extracted |
-sv or --style-violation
|
If set, the code style violations are extracted |
-cc or --code-complexity
|
If set, the code complexity are extracted |
-cores or --cpu-cores
|
The number of threads. The default value is ALL logical cores on the system. |