I am dealing with a team of unmotivated sf dev/configurators. They are either refusing to learn git or are just slow. So, asking them to start the dev process using git and IDE is bringing in more unstability then agility. Our organization wants to adopt more agile way of doing things rather. So we want to implement some in-house pilot continuous integration and deployment process.
Since the usage of git is becoming a bigger challenge, i am kind of thinking to allow them to deploy their changes to to the
sharedDEV using the old fashion
changesets (which they are familiar with).
And i am setting up a Jenkins job to pull/retrieve the metadata from this
sharedDEV org and version control it. The delta changes will be pulled in as we repeat this process again an again. And once they are in the source control, i will build the src components and package.xml based on the diff to validating and deployment to higher environments/orgs.
Question: Have anyone done this approach? And does any of the SF experts here foresee any issues with it?
NOTE: i am not looking for commercial product recommendations (like autorabbit, gearset ....etc )