In http://jazz.net/forums/viewtopic.php?p=34452, I inquire
about checking in the output of the BF .export directive in RTC
during a build so we can get some semblance of version control
of our Build Forge projects together with the code being built...

On a more general note however, we're wondering... Are there
any plans to support an SCM integration for Build Forge projects
themselves? I know I can use .export at build time. At the very
least, I think it would be helpul to be able to export the project
from the GUI so it could be manually checked in to whatever SCM
system is in use. The workflow I imagine is that we'd go to the BF
console, make our changes, check out the BF project XML file from
source control, "Save Project As..." to the file under source control
and check in. Then we'd go about building, iterating in BF, etc.

Any hints as to what might be coming in this area and/or best
practices for keeping BF projects under version control would be
welcomed.

I think you might be looking for a way to deal with "build artifacts" in general, with the project definition (your exported project.xml) one of the artifacts of that particular build (a point in time statement). We are looking into mechanisms to allow publishing of build artifacts associated with the Build Forge job, similar to how the RTC Build Toolkit Ant Tasks allow you to upload logs/files and links to the Build Result. As mentioned in the other forum posting, you can publish the project.xml (after .eusing the Ant Toolkit in a Build Forge step back to the RTC build result if you have that integration setup. You need to make sure the Build Forge server connector that you use sends back the buildResultUuid property. This is needed as a parameter of the Ant publishing task to link to the proper build result. You can find the connector you can use in the following article: https://jazz.net/wiki/bin/view/Main/RationalBuildForge/CallingBuildToolkitAntTasksFromBuildForgeToFeedContributions.

There's also the existing Build Forge snapshot function which isn't exactly for versioning where every single change is captured, but let's you create a snapshot at various intervals of your Project design.

Let me know if you have any additional requirements related to this.

Regards,
Pete