Are you talking about the revision number from your source control system or the Talend version number of the job incremented when you upload it to the cloud?
You can always execute any command line program with the tSystem component. You could run the command for your source control system that gives you the information you need and then output it with a tWarn, e.g.
However, this would only work if SVN is available at runtime.
Suppose the SVN repository is only available in my development environment, but not in my production environment. The job would not be able to query a revision with the tSystem component at runtime.
So I'm looking for a way to store the HEAD revision in the build and roll it out with the job.
If you are using continuous integration for your deployment pipeline you could write a small shell script that writes the revision somewhere per my original suggestion and then have your job read that revision. If you use Jenkins or some other CI system it should be fairly easy to do.
You could also write a web service that returns the svn revision or whatever data you need and that way your job could access the web service from anywhere.
You use case is not a common one so I don't think there are components in Talend that would do it across all platforms. You will have to create a way to do it.
