I used the Scheduler export script available under <DENODO_HOME>/tools/scheduler to take a backup of the scheduler projects which contained all jobs and its related information dumped as a zipset. This zipset can be maintained in a VCS like git. Also, I found out that the Scheduler Developer API has methods to export and import objects to Scheduler which can export any of the specific jobs if you need it. You can read more about the export scripts
and scheduler developer API in [Export](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/appendix/use_of_the_importexport_scripts_for_backup#export) and [Developer API](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/developer_api/developer_api) sections of Scheduler Administration Guide.
I dont believe there is a out of box integration with VCS on Scheduler as is the case with Virtual DataPort where Views are protected by VCS against modification. The reason partly may be due to the fact there is not a common "Language" to define the scheduler jobs, as opposed to "V(irtual)Q(uery)L(anguage" for Virtual DataPort views. We can write our own way of managing the jobs versioning with above said options.
Hope this helps!