![]() |
![]() |
Parabuild provides a version control parameter that allows setting an arbitrary location for a checkout directory. This feature is useful when it is necessarily to reduce length of file paths to avoid hitting the path length limitation under Windows, or when your software requires to be run at a pre-defined directory:

Parabuild now supports regular expressions in the ignore lists. This feature allows configuring arbitrary paths that Parabuild will ignore when looking for changes in a version control system:

Now a build configuration has an option to use either p4 login or of P4PASSWD for authentication:

Now it is possible to use in all elements of a Perforce client view in a build configuration:

Parabuild provides a configuration option for Perforce builds not to update have list when it populates the local workspace. This option is typically used where there is no need to track the state of the workspace after it has first been synced. It may speed up syncs and reduce locks on the Perforce database:

Now it is possible to limit the number of change lists retrieved as a part of the change wait cycle. Large code bases may benefit from this option:

Now it is possible to store a client view for a build under control of Perforce. Some change management infrastructures require storing a client view in Perforce, and this feature allows for this:

To avoid checking out the whole path, Subversion-based build confirmations can now add "-N" to the repository path in Parabuild

Now build infrastructures using CVS 1.4 and newer as a version control system can enjoy fast detection on changes. The speed improvement for large codebases may reach times:

When building a CVS branch, Parabuild provides a shell variable PARABUILD_CVS_BRANCH. The variable contains a name of the branch.
| « New features in notification |