Build and Package A Module from therepo ¶

Table of Contents

Build and Package A Module from therepo

Prerequisites ¶

Docker installed and correct container type is selected (if on Windows Host OS)
Fuzeapp installed.
workspace.ini file created and located in C:\code (Windows) or ~/code (Linux or MacOS)
Workspace created with therepo

Your workspace file system looks like:

c:\code or ~/code
    - workspace.ini
    - \therepo

Build and Package release target of a Product ¶

Execute the following commands:

$ cd ~/code
$ fuze --build-map therepo/build/mybuildmap.json --target release --package release

Building “all” Package Targets ¶

As with the build targets, you specify a particular package target (as you did above), or you may ommit a specify target, in which case all package targets will be created. The following will build all targets and all packages:

$ fuze --build-map therepo/build/mybuildmap.json --package

Warning

Package targets may be tightly coupled to one or more build targets, depending upon the build map design. Fuze cannot predetermine whether you have specified compatible build and package targets.

Success Indications ¶

If successful, you will see the following indications in the stdout:

++++++++++++++++++++++++++++++++
[product] build status: SUCCESS
++++++++++++++++++++++++++++++++

...

++++++++++++++++++++++++++++++++
[product] packaging status: SUCCESS
++++++++++++++++++++++++++++++++

...
++++++++++++++++++++++++++++++++
Fuze ID is <FuzeID>
++++++++++++++++++++++++++++++++

Package Output Location ¶

If successful, you will find the package in your FTL. Fuze stdout will tell you where. For example:, In this case:

Local package "release-product-v1.0.<fuzeid>.zip" is at ~/tmp/ftl/<fuzeid>/release-product/release

Build and Package A Module from therepo¶

Prerequisites¶

Build and Package release target of a Product¶

Building “all” Package Targets¶

Success Indications¶

Package Output Location¶