We can version control the elements in the database such as data sources, views, and web services, and also custom i18n maps and jar extensions that are particular to the database. But we cannot version the elements that are global to the server like users, roles, database settings. You can refer to the document [Supported Element Types](https://community.denodo.com/docs/html/browse/7.0/vdp/administration/version_control_systems_integration/vcs_integration_features/supported_element_types) of the Virtual DataPort Administration Guide.
The Scheduler jobs cannot be integrated with Gitlab for version control since there is no common “Language” to define the scheduler jobs.
In order to maintain the Scheduler Jobs in Gitlab, I would use the Scheduler [export](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/appendix/use_of_the_importexport_scripts_for_backup#export) script available under <DENODO_HOME>/tools/scheduler to export all metadata and configuration of a Scheduler server as a zip file that contains all jobs and its related information. The generated file can be maintained in GitLab. Also, I found out that the Scheduler [Developer API](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/developer_api/developer_api) has methods to export any of the specific jobs.
For more information, you can refer to a similar community question [Integrate Scheduler Projects with GIT](https://community.denodo.com/answers/question/details?questionId=9060g000000TRB3AAO&title=Integrate+Scheduler+Projects+with+GIT).
Hope this helps!