I've been looking for a way to use git/github for source code control for our Jitterbit (JB) projects.
Our current solution is for one dev to manually type out and explain the changes they've made in a README file within the JB project noting what scripts, transformations, operations, etc. have been changed and what line numbers the changes were made on.
Then to 'approve' the changes, another dev needs to open that project in the JB design studio, read through the README file, hunt down the object that was changed, find the line(s) noted in the README file and review the changes. Email or Slack back and forth to discuss any issues. Rinse and repeat for each object changed.
It's very cumbersome and time consuming.
While I can certainly create a repo in the JB projects folder, that's less than desirable because even with a one line change in a JB script, there are a lot of unrelated metadata changes (related to the JB environment, etc.) that show in the diff that have nothing to do with the actual code changes a dev makes. This gets even more complicated when you start switching environments in JB.
I've looked at using a .gitattributes file with a filter that uses sed to remove metadata lines from files (JB stores them as .xml files) that have actual dev code changes, but that's a very clunky and error prone solution, at best.
Has anyone figured out a way to use source control with JB, or, at least, some sort of diff tool solution where one dev can easily see, review, comment on, and approve/deny changes a dev makes (basically, everything that git provides...or at least the diff part)?
