I think the ts_sal/Jenkinsfile needs some attention.  It looks like there is some duplication between the C++ and Java unit test stages; both are generating the Script and Test libraries.  I recommend splitting the salgenerator steps out into a separate stage and NOT running them in the unit test stages.

Additionally, to make parsing the Jenkins build console-output easier, instead of the using a single docker exec command with multiple command separators (&&), split it up into multiple docker exec commands.  That way the commands bookend the processes and make debugging easier.