My nightly build sequence consists of the following:
- check out source code
- update buildNumber.properties file (using ${build.version} taken from QuickBuild environment)
- check in buildNumber.properties file
- build, test, post artifacts, etc.

Currently I am having to perform the third action via a command-line step. However, this requires my build scripts to be aware of the SCM tool they are using.
Since different projects use different SCM tools (we have code in Git, Subversion, and Perforce), the method to perform this check-in varies, sometimes by a lot.

I noticed that, under the proof build support options, there is an option to automatically check in any local changes at the end of the build,
if the build is successful. However, I need this to happen earlier in the build, and not tied to preflights.

I am looking for a step type 'Repository -> Checkin' which would commit any local changes to the workspace at the time the step is run. Possible options include:
- a username/password combination to use to check in (or, maybe this needs to be a property of the Repository itself)
- a checkin comment
- a subset of files to check in, or a mask of files to include/exclude
- options for how to react in case of conflicts