Tip: Add files that are important for collaboration to a version control system.
Usage of version control systems with DaVinci Developer Adaptive is helpful for managing model changes over time as well as enabling co-workers to work on the models in parallel and ensuring reproducibility of artifacts. If the selection of files to include is not done thoughtfully, it can however lead to merge conflicts or reduced efficiency. For example, some files such as object files contain content that is non-readable for humans and are thus usually not version controlled.
The following files are recommended to be version controlled:
- Project definition files that are needed in order to import the DaVinci Adaptive Project correctly, such as the PROJECT and ADPA files.
- Project settings that should be shared within the team(s) working on the project, such as the list of validation rules that are not regarded as applicable in acknowledgements.dc or the project dependencies stored in the ADPA file.
- The AUTOSAR model files, in other words the ARXML files stored in the model project folder. Usually, both external input files and files created by the team are version controlled.
- Scripts executed by several team members or teams, such as the content of the script project folder.
The following files are often not version controlled, unless it would be beneficial for the respective workflow:
- User settings that are only relevant for a specific user rather than a team, for example preferred window sizes or Model Scopes stored in the DCUSR files or the MICROSAR Adaptive BSW Package installation path stored within the workspace .metadata directory. It is more common to store the expected MICROSAR Adaptive BSW Package version than its installation path, as the path used often differs between workstations.
- Temporary directories, such as the .tmp directory.
- Generated artifacts, as they should be possible to reproduce if the same ARXML files, MICROSAR Adaptive BSW Package, and DaVinci Developer Adaptive version are used. Thus, the version numbers are often more likely to be stored than the CCP, H, and JSON files within the generation output directory unless the content is vital for documentation purposes.
- Generation reports stored in the .adpa/log/ directory. In cases they are important for documentation purposes of a delivery, they are usually stored together with the delivered artifacts.
- The MICROSAR Adaptive BSW Package itself is usually not placed in a version control system due to its size and as it contains several non-human-readable files. Moreover, is recommended to store the complete BSW Package in one location rather than splitting its content into several artifact storage systems.
- For similar reasons, the DaVinci Developer Adaptive tool is also not recommended to be stored in a version control system.
What files are most suitable to store in each system, however, is unique to each context and needs to be decided in each respective environment.
In case you are using Git for version control, DaVinci Developer Adaptive provides the following features:
Add .gitignore File
You can add a pre-filled .gitignore file to your DaVinci Adaptive project as follows:
New DaVinci Adaptive Projects
When creating a new DaVinci Adaptive project, activate the check box to create a .gitignore file during Project Setup.
Existing DaVinci Adaptive Projects
For existing DaVinci Adaptive projects, click the context menu command 
Add .gitignore File of the respective DaVinci Adaptive project in the DaVinci Project Explorer.
Edit .gitignore File
Click the context menu command 
Edit .gitignore File of the respective DaVinci Adaptive project in the DaVinci Project Explorer to open the .gitignore file in the text editor where it can be edited.