You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For instructions on how to contribute enhancements and bug fixes to zAppBuild, please read the [Contributions Guidelines](CONTRIBUTIONS.md).
14
17
15
18
## How zAppBuild works
19
+
16
20
The zAppBuild repository is intended to be cloned to a single location on Unix Systems Services (USS) and used to build all of your z/OS applications. Global configuration properties are configured in the properties files in the [build-conf](build-conf/) directory. Specifying application-level properties is done by simply copying the supplied `application-conf` folder (located in the [samples folder](samples)) to the application source repository you want to build and then verify/update the contained default configuration property values to ensure they meet the build requirements of your application. See the included [MortgageApplication](samples/MortgageApplication) sample for an example of an application that has been modified to be built by zAppBuild.
17
21
18
22
**IMPORTANT** : The [datasets.properties](build-conf/datasets.properties) must be configured for your build machine before executing a build! See [build-conf/README.md](build-conf/README.md) for more information.
19
23
20
24
## Supported Languages
25
+
21
26
The zAppBuild sample provides the following *language* build scripts by default:
27
+
22
28
* Assembler.groovy
23
29
* BMS.groovy
24
30
* Cobol.groovy
@@ -37,11 +43,13 @@ The zAppBuild sample provides the following *language* build scripts by default:
37
43
All language scripts both compile and optionally link-edit programs. The language build scripts are intended to be useful out of the box but depending on the complexity of your applications' build requirements, may require modifications to meet your development team's needs. By following the examples used in the existing language build scripts of keeping all application specific references out of the build scripts and instead using configuration properties with strong default values, the zAppBuild sample can continue to be a generic build solution for all of your specific applications.
38
44
39
45
## Build Scope
46
+
40
47
The build scope of zAppBuild is an application which is loosely defined as one or more Git repositories containing all the z/OS source files required to build the application. There are no specific rules as to the structure of the repositories except that one repository must contain the high level `application-conf` folder provided by zAppBuild which contains all of the configuration properties for building the application programs.
41
48
42
49
**NOTE:** All source repositories that make up the application must be cloned on the build machine under a common *workspace* directory prior to calling build.groovy.
43
50
44
51
zAppBuild supports a number of build scenarios:
52
+
45
53
***Single Program** - Build a single program in the application.
46
54
***List of Programs** - Build a list of programs provided by a text file.
47
55
***Full Build** - Build all programs (or buildable files) of an application.
@@ -51,8 +59,9 @@ zAppBuild supports a number of build scenarios:
51
59
***Merge Build** - Build only changed programs which will be merged back into the mainBuildBranch by using a triple-dot git diff.
52
60
***Scan Source** - Skip the actual building and only scan source files to store dependency data in collection (migration scenario).
53
61
***Scan Source + Outputs** - Skip the actual building and only scan source files and existing load modules to dependency data in source and output collection (migration scenario with static linkage scenarios).
54
-
***Build Preview** - Supplemental build option. Process all phases of the supplied build option, but will not execute the commands. A build report and a build result are generated with a specific status that excludes them in subsequent impact build calculations.
62
+
***Build Preview** - Supplemental build option. Process all phases of the supplied build option, but will not execute the commands. A build report and a build result are generated with a specific status that excludes them in subsequent impact build calculations.
55
63
64
+
To check how to get started with zAppBuild, see [Getting started with zAppbuild](./docs/GettingStarted.md) section.
56
65
57
66
Instructions on invoking a zAppBuild is included in [docs/BUILD.md](docs/BUILD.md) as well as invocation samples for the above mentioned build scenarios including sample console logs.
58
67
@@ -63,6 +72,7 @@ zAppBuild comes with a set of reporting features. It helps development teams to
63
72
Links to additional documentation is provided in the table below.
64
73
65
74
## Repository Legend
75
+
66
76
Folder/File | Description | Documentation Link
67
77
--- | --- | ---
68
78
build-conf | This folder contains global configuration properties used by build.groovy and language build scripts. | [build-conf/README.md](build-conf/README.md)
# default copies all dependencies into the dependency dataset definition which was previously passed to the utilities/BuildUitilities.copySourceFiles method
# default copies all dependencies into the dependency dataset definition which was previously passed to the utilities/BuildUitilities.copySourceFiles method
0 commit comments