Pipeline Service¶

This article is part of the work in progress Pipeline V3. Documentation is written as it is being developed. It does not apply to the current build pipeline.

Overview¶

The build pipeline consists of one service application, which can be run as either master or slave. You must run at least one master, either locally or on an external build server. Slaves may be run additionally, either locally for each additional simultaneous build process you wish to run, or externally for each simultaneous build process on an external server.

All build services must be able to connect to the same network hard drive for reading leveldesign and database, as well as for writing build output. This may also be a local path if you are running all services locally on one machine.

A Pipeline Client application may be used to connect to the master pipeline service remotely. The client does not need to be able to have access to the network hard drive. The service allows the client to browse trough build file structures remotely, call commands, list build input and output errors, etcetera.

Configuration¶

Configuration values for the service are under pipeline_service.cfg for both the master and slave. Defaults are under pipeline_service_default.cfg. You must only modify pipeline_service.cfg.

Directory paths may be different for different services, as long as they point to the same physical location.

MasterSlavePassword must be the same on all build services.

MasterAddress and MasterPort must be configured to point to the machine running the master service, or set to "127.0.0.1" for running locally.

Workspace¶

The build workspace is configured using georges sheets. Refer to process specific manuals for more information.

FAQ¶

How to setup the pipeline locally?¶

• Configure the pipeline_service.cfg with MasterAddress set to "127.0.0.1", and set all directories.
• Run pipeline_service_master_r(.exe)
• For each additional simultaneous process you want, run pipeline_service_slave_r(.exe)