Builds and Build Definitions without Source Code?
Accepted answer
Comments
Do you have a high level approach you can share regarding that first client example?
One other answer
As far as I can tell, at least for EWM, the build definition itself does not provide a lot of value. The Build definition is only referenced within the build loop in EWM. You need a build result that has been created using the build definition to achieve anything in EWM.
I do not know where build definitions show up in RQM and what they are used for.
Comments
But in general can builds be used for non-software items? Like documentation, drawings, spreadsheets, etc. stored in RTC SCM?
Builds execute one or typically more steps to produce an outcome. You can use them for whatever you want, with or without accessing the SCM system. If there is automation available, it can potentially be included. E.g. generation of documentation (e.g. JavaDoc), running some tool to extract and compute information, routing, maybe pulling in mechanics data.
The build result is something that usually ties the input and output together, to make it reproduceable. It is also possible to store the total build input and result data. Usually this would be done in a binary repo such as Artifactory and not EWM SCM.
For storing the cumulated build data, see some thought here: https://rsjazz.wordpress.com/2015/10/28/build-artifacts-publishing-and-automated-build-output-management-using-the-plain-java-client-libraries/