Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added documentation of object decks with deployType #551

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

M-DLB
Copy link
Collaborator

@M-DLB M-DLB commented Oct 14, 2024

This PR adds a "deploy type" to all Object decks generated during the build process. Object decks are now documented in the DBB Build Report, with an object type "OBJ". Object decks can be then processed and potentially integrated in the archive.

Copy link
Member

@dennis-behm dennis-behm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer a new setting this name via a build property, similarly to the other deployTypes.

This is the sample for COBOL -

#
# default deployType
cobol_deployType=LOAD
#
# deployType for build files with isCICS=true
cobol_deployTypeCICS=CICSLOAD
#
# deployType for build files with isDLI=true
cobol_deployTypeDLI=IMSLOAD
#
# deployType for build files with isIMS=true
cobol_deployTypeIMS=IMSLOAD

For COBOL, it could be cobol_deployType_object, or cobol_object_deployType.

What are your thoughts on it?

@M-DLB
Copy link
Collaborator Author

M-DLB commented Oct 14, 2024

The problem is that we need to parse the build report afterward to extract these artifacts based on their deploy type. We could add a property for each type of artifacts, but it means we would need to add a property in packaging scripts to specify what is the deploy types associates to object decks. Do you want to add more properties?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants