Using express builds to prevent winkin to other views
Learn how to use express builds to prevent winkin to other views.
During an express build, HCL VersionVault creates DOs that are nonshareable and cannot be used by builds in other views. These nonshareable DOs have configuration records, but the VersionVault build tools do not write information into the VOB for these DOs. Therefore, the DOs are invisible to builds in other views.
Use express builds when DOs created by the build are not appropriate for use by other views. As a general rule:
- Use express builds for development builds that use relatively unstable, checked-out versions.
- Use regular builds for release or nightly builds that use stable, checked-in versions. DOs created by these builds are more likely to be winked in by other views.
Enabling express builds
When you invoke a VersionVault build tool, the kind of build that occurs depends on how your view is configured. To use express builds, configure an existing dynamic view with the nonshareable DOs property or create a new dynamic view with the nonshareable DOs property. Then, run your VersionVault build tool (clearmake or clearaudit) in the view.
The below content describes how to configure your view to use express builds.
Configuring an existing view for express builds
Use the command chview -nshareable_dos view-tag. For more information, see the chview reference page.
Future builds in the view will create nonshareable derived objects. However, existing DOs in the view are shareable; they are not converted to nonshareable. These existing DOs can still be winked in by other views.
Creating a new view that uses express builds
To create a new view, enter the mkview command and specify the -nshareable_dos option. For more information, see the mkview reference page.