Dependencies

A project's dependencies are prerequisites for a build of that project. More specifically in pulse™, projects may depend on other projects. When a dependency relationship exists, builds may be triggered using dependent build triggers and artifacts may be transferred between builds using publication and retrieval.

As an example, a common dependency would be from a product project to a library project. The library provides general-purpose APIs packaged as an artifact like a Java .jar file or a native .lib library. The product build links to this library so that it can use those APIs. By setting up a dependency relationship in pulse™, the library artifact can be delivered from builds of the library project to those of the product project. Builds of the product project may also be triggered when builds of the library project complete and publish a new version of the artifact.