| Builder 2 impact on builder 1.x users |
|
Builder 1.x users should have no problem migrating to builder 2. There are some important differences though, that must be considered:
- Configuration files are not compatible between versions
Builder scenarios will need to be freshly configured after installing builder 2. Most of the data will be the same, but the direct use of builder 1.x scenarios is not supported - nor is there any automatic conversion (not yet, anyway).
A good procedure would be to use builder 1.x to execute "builder -d -p<product> -s<scenario>" on the builder 1.x scenarios and print out the results.
Then use these as reference for creating the new scenarios.
- MRG States getversions do NOT automatically include higher states
Builder 1.x had a built-in assumption that a "submitted" MR node, for example, should contain all MRs in submitted and beyond, short of approved. This assumption was widely held, and was partly due to the assumed "cumulative" nature of source nodes. Now that builder can easily accommodate MR rejections and promotions, that assumption is no longer appropriate.
With builder 2 you can configure a node to have ONLY submitted MRs, and another that has ONLY preitpassed MRs, and then Viewpath through the both of them.
Or, to get it to behave like builder 1.x, simply configure builder to select MRs from all the states that you wish. Builder 2 allows for multiple state getversions on a single node.Of course, Builder still includes the assumption that higher level MRs should be in the UMR list.