Publishing your Binaries


You can publish your Binaries to the central Repository as part of your Build processing.  Publishing your binaries allows you to assign a Status to your Build Results, and provide a central location for downloading the build results for both current and past build results.  The Binary Repository serves as a central reference location from which your deployments can be managed across the lifecycle.  Deploy+ can use the Meister Binary Repository to track and verify software deployments.


You publish your binaries to a Collection within the Binary Repository. A Collection is a subdirectory of the Binary Repository where your binaries and other required deployable files will be stored and referenced.  Because each Collection will potentially store multiple versions of the build, the Collections are stored based on the Build Number generated as part of the Workflow


To publish your binaries use the “Publish Binaries” Workflow Activity Group, found when you select “Add Activity” from the Eclipse RCP Workflow Editor, Activities Tab.  You can publish your build results from either a Meister Build, or from an external build script such as a Make, Ant or Maven script. 


When publishing the build results, you will need to specify the Collection name as well as the files you wish to store in the Repository.  When using Meister to manage your build, you can specify one or more Meister Build Control files (i.e. Windows.mak, Java.mak, Aix.mak, Hpux.mak, Linux.mak or Solaris.mak).  The Meister Build Control File will be used to determine what files need to be archived to the Repository.  If you are using a external manual script for managing the build, you will need to list the files, using wild cards to include in the archive process (i.e. *.exe, .dll, *.jar).  In either case, you can add other files that you may wish to include in the archive, such as a Meister Build Audit Report.