-
Notifications
You must be signed in to change notification settings - Fork 135
/
Copy pathpackageBuildOutputs.properties
99 lines (85 loc) · 4.49 KB
/
packageBuildOutputs.properties
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
########################################################################
### The following properties are configure the packaging step
########################################################################
# required mapping of last level dataset qualifier to DBB CopyToFS CopyMode
# DBB supported copy modes are documented at
# https://www.ibm.com/docs/api/v1/content/SS6T76_1.1.0/javadoc/com/ibm/dbb/build/DBBConstants.CopyMode.html
copyModeMap = ["COPYBOOK": "TEXT", "COPY": "TEXT", "DBRM": "BINARY", "LOAD": "LOAD", "JCL": "TEXT", "EQALANGX" : "BINARY", "OBJ" : "BINARY"]
# Comma-separated list of deployTypes to limit the scope of the tar
# file to a subset of the build outputs. (Optional)
# Please not that the cli option `deployTypes` overwrites this setting
# Sample: deployTypesFilter=CICSLOAD,BATCHLOAD
#
# deployTypesFilter=
# Comma-separated list of deployTypes that describe >public interfaces<
# that consuming applications pull into their build workspace as a build
# dependency.
#
# Along with the the usage definition 'service submodule' in the
# 'Application Descriptor', these outputs will be made
# available in a dedicated sub folder of the tar file, that
# applications that need these modules as a build dependency
# can include into their build scope/workspace.
#
# These deployTypes are excluded from being added to the /bin folder
# that contains the deployable outputs.
#
# This is specifically useful for applications that provide object modules
# of statically called submodules to other applications.
# It does not effect modules that are called dynamically.
publicInterfacesDeployTypes=OBJ
# Comma-separated list of deployTypes that describe derived build outputs
# that represent >private interfaces< that are required internally for by
# the application
#
# Along with the required usage definition in the
# 'Application Descriptor', these files will be made available
# in a dedicated sub folder 'lib' of the tar file, that
# can then be included as a baseline package.
#
# These deployTypes are excluded from being added to the /bin folder
# that contains the deployable outputs.
#
# This is useful for applications with static calls to provide object modules
# of statically called submodules or generated source code such as
# generated copybooks for BMS or DCLgen files for subsequent builds.
privateInterfacesDeployTypes=OBJ,BMSCOPY
# Publish source code interfaces that are declared as 'shared/public' in the
# 'Application Descriptor' into dedicated subfolder for consumption by
# applications that depend this application.
# The packaging process retrieves the files directly from the
# checked out Git repository.
publishInterfaces=false
# Comma-separated list of files/patterns from the USS build workspace. (Optional)
# Please note that the cli option `includeLogs` overwrites this setting
# Sample: includeLogs = *.log,*.xml
#
# includeLogs =
# Boolean setting to define if file the deployType should be added as the file extension
# Please note that the cli option `addExtension` can override this setting and activate it.
# Default: false
addExtension=true
# Boolean setting to define if the Wazi Deploy Application Manifest file should be generated
# Please note that the cli option `generateWaziDeployAppManifest` can override this setting and activate it.
# Default: false
generateWaziDeployAppManifest=false
# Boolean setting to define if the IBM Concert Build Manifest file should be generated
# Please note that the cli option `generateConcertBuildManifest` can override this setting and activate it.
# Default: false
generateConcertBuildManifest=false
# Boolean setting to define if SBOM based on cycloneDX should be generated
# Please note that the cli option `generateSBOM` can override this setting and activate it.
# Requires the classpath to contain the cycloneDX libs
# Default: false
generateSBOM=false
# Boolean setting to define if the ArtifactPublisherHelpers should be invoked to upload the package to the configured
# binary artifact repository, see appArtifactRepository.properties (--artifactRepositoryPropertyFile) or the individual configurations
# Please note that the cli option `publish` can override this setting and activate it.
# Default: false
publish=false
# Name of the default tarFileName
# When processing a single build report, the DBB Build report label it used as the tar file name
# When processing multiple build report, 'Default' is used as the tar file name
# tarFileName=
# File encoding for generated files such as Wazi Deploy Application Manifest file
fileEncoding=UTF-8