In a Data Integration-oriented Production environment, the only tools needed are:
the Talend Administration Center application to schedule the execution of the Jobs,
an execution server, to deploy and execute the Jobs,
(the Repository Manager to pass items to the QA and Production environments).
The Job generation step is indeed skipped as Talend Administration Center is able to retrieve pre-generated Jobs from archive files. The CommandLine application is thus no longer needed.
Likewise, the Production environment does not require to be linked to SVN or GIT as the Jobs that were pre-generated in the previous environments can be imported and executed in a "no-storage" project. For more information on this type of project, see the Talend Administration Center User Guide.
Best practice: Once a feature is released or a bug is fixed, the best practice is to use SVN or GIT branches and tags to record this change of status. They are used to identify a specific version of a project at a given time, for example the feature that has been developed, tested and validated, and to identify the environment used to make the feature work (CommandLine/Job versions, project properties etc.).