EWM 7.0.2 - SCM Component Baselines and Deployment
Dear all,
One answer
Hi Glyn.
When you create a snapshot and there is a change on a component that is not in the latest baseline, the snapshot would always create a new baseline. Just to make sure this is understood.
Build definitions for the JBE can have a tab Jazz Source Control. If you have a repository workspace created from the snapshot, you could use that to perform a load operation to load the files under SCM. This option is configurable, but not to an extend to have filters.
In Jenkins, you could load SCM from a snapshot - but you have to provide the name in the build.
You could use the SCM Command Line and create a tool that loads the files into a location you want and delete the files you do not want. Or you could see if you can make the scm command line tool only load the files you want.
You can compare snapshots and builds can create snapshots that you can use to compare. You can use the SCM command line to do the compare and use the output for reporting.
Comments
Hi Ralph, thanks. Your first sentence I had not realised. The work around it seems is to create a work space which doesn't flow to a stream, then manually add the latest valid baseline for a component.
You could see the issue, if you see baselines that have the name of the snapshot.
You should also be able to see this in the pending changes view. I think there is a markup for components that are beyond a baseline somewhere. But yes, you can add specific component baselines to a workspace or stream.