OpenMake Meister Binary Repository
Referencing binaries from the OpenMake Meister Build System.
OpenMake Meister Repository Details
If you automate your builds (compile/link) using OpenMake Meister, DeployHub Pro pulls binaries from the Meister binary repository that your Component uses. Following is a list of the details for connecting a Meister repository to DeployHub Pro:
| Field | Description |
|---|---|
| Buildnumber | The identifier of the Build that resides in the Meister Repository. |
| Buildnumber Encrypted | Select the box to indicate if the Build Number should be hidden in the database. |
| Buildnumber Override | Select the box if the Build Number can be replaced at the Component definition. |
| Filepath | The fully qualified directory name to the files in the OpenMake Meister repository that will need to be deployed. |
| Filepath Encrypted | Select the box to indicate if the Filepath name should be hidden in the database. |
| Filepath Override | Select the box if the Filepath can be replaced at the Component definition. |
| Pattern | This defines the file types you want to pull from the Repository, such as *.exe, *.dll, *.war. |
| Pattern Encrypted | Select the box to indicate if the Pattern should be hidden in the database. |
| Pattern Override | Select the box if the Pattern can be replaced at the Component definition. |
| Recursive | Select the box in order to cause the Repository to return all of the files from directories below those designated by Filepath. |
| Recursive Override | Select the box if the Recursive option can be replaced at the Component definition. |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified September 5, 2024: Signed-off-by: tracyragan <[email protected]> (fd10ef7)