Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page

Was this helpful?

  1. Services

Pipeliner

The Pipeliner service primarily job y to allow the user to pipeline Jobs and run them either in parallel and/or after a previous set of jobs finished.

This allows you to create many jobs to sync all your content types, and run all the jobs by starting a pipeline rather than running every single job. Effectively, "pipelines" are a collection of "steps" and "steps" are a collection of "jobs."

Responsibility 1: Allows the user to create a "Pipeline" of jobs.

Responsibility 2: To execute a Pipeline, meaning, to execute each of the sync jobs configured within the Pipeline. A pipeline will run all the steps in order. When a step is run, all the jobs in a step will be run at one time.

PreviousDropoff TaxiNextScheduler

Last updated 2 years ago

Was this helpful?