Configuring Publishing Containers

The Publishing Containers are separated into two components:

Task Executor Container - Executes various tasks, such as building deliverables.
Publishing Main Container - Manages deliverables, the templates used by deliverables, and the builds associated with a deliverable.

You can configure the containers by setting some properties to customize and optimize the behavior of the publishing and build processes according to your specific requirements.

Configuring the Task Executor Container

For the Task Executor container, you can configure the following properties:

executor.service.ope.max.memory: Specifies the maximum memory allocated for a single publishing build. Default value is 1024 MB.
executor.service.validation.max.memory: Specifies the maximum memory allocated for a single validation build. Default value is 200 MB.
executor.service.parallel.publishing.builds: Defines the maximum number of publishing builds that the application can execute simultaneously. This limits how many publishing processes can be handled at once, helping to manage server load and optimize resource usage. Default value is 2.
executor.service.parallel.validation.builds: Defines the maximum number of validation builds that the application can execute simultaneously. Controls how many validation processes can occur at the same time, ensuring efficient validation processing while balancing server performance. Default value is 5.
executor.service.metrics.disk.store.period: Determines how long (in days) the server should retain publishing build metrics on disk. This ensures that metrics for builds are stored for a limited time, preventing disk space overuse by automatically purging old data after the specified retention period. Default value is 30.

Configuring the Publishing Main Container

For the Publishing Main container, you can configure the following properties:

publishing.service.deliverable.builds.number: Sets the number of builds to retain for each deliverable. This helps manage disk space while maintaining only the most recent builds. Default value is 3.
publishing.service.allow.automatic.builds: Controls whether or not automatic builds (triggered by remote modifications or scheduled tasks) are allowed. Default value is true.
publising.service.check.remote.period: The interval (in seconds) at which the system checks for remote changes. Default value is 60 seconds.
publishing.service.start.build.remote.changes.period: The delay (in minutes) before starting a build when remote changes are detected. If additional remote changes are detected during this period, the build is re-triggered. Default value is 3 minutes.
publishing.service.start.build.remote.changes.max.period: The delay (in minutes) before starting a build when remote changes are detected. If additional remote changes are detected during this period, the build is not re-triggered. Default value is 10 minutes.
publishing.service.build.console.max.lines.numbe: Specifies the maximum number of lines displayed in the console that shows the transformation progress. Default value is 1000 lines.