Problem: PipelineService slows down the start of the AppServer.^[60]

Reason: Pipelines are never cleaned up and the database can get bigger and bigger.

Solution: As of V12.7 there is a CleanupPipelinesTask to cleanup finished pipelines. It is enabled per default. If there is no further specification given, pipelines will be cleaned up after 30 days.

Dashboard: CleanupPipelines

Default settings are the following:

Pipelines without type are removed after 30 days, failed nativecheckin pipelines after 5 days and succeeded nativecheckin pipelines after 2 days.

Furthermore it is possible to specify pipeline types and states manually on file level:

partwarehouse\pipeline.cfg

Default:

#:Help;Settings to cleanup pipelines by type and state used by CleanupPipelinesTask
[Cleanup]
#:HELP
default=30
nativecheckin(failed)=5
nativecheckin(succeeded)=2

In addition:

Pipelines are saved under $CADENAS_SETUP\pipelines.

In *.pwp, under attribute "pipelineType" the type is given, which then can be used in the configuration file pipeline.cfg.

Example "clswizpipeline.pwp"

Schema:

type(state)

After "type" the "state" is given in brackets. Possible values for "state" are "succeeded", "failed" and "cancelled".

Example:

clswizard(failed)=10
clswizard(succeeded)=10

Combinations are also possible:

Example:

clswizard(failed,cancelled)=2