LIBNOVA DOCS Home
Pipelines module
Pipelines module
  • Pipelines Module Definition
    • Pipelines Module
  • Benefits and importance of the Pipelines module
  • Pipeline Metadata Definition (Metadata Schemas)
  • Creating a new Pipeline
  • Pipelines details
  • Target selection and object filtering (Triggers)
  • Execution/launching and review restrictions
  • Steps
  • Monitoring the progress of your pipeline tasks (Jobs)
  • Filtering jobs
  • Jobs and API access
  • Running a pipeline on a given container
  • Branching
  • Wait for user step
  • Automating your pipeline (using a function)
  • Stopping a running job
  • Pipeline Details
Powered by GitBook
On this page

Filtering jobs

Filtering jobs by Container, Date (range), User, Status, and Result allows you to quickly narrow down and organize tasks in a pipeline.

  • Container: Filters jobs based on specific environments or containers where they are executed.

  • Date (range): Limits the jobs shown to a specific time period.

  • User: Shows jobs initiated by a particular user.

  • Status: Filters by the current job state, such as running, completed, or failed.

  • Result: Narrows results based on job success, failure, or other outcomes.

This enhances task tracking and monitoring efficiency.

Making decisions with pipelines involves using conditional logic to control the flow of tasks based on specific criteria or outcomes.

These decisions can include branching to different steps depending on data quality checks, job results, or the availability of resources.

For instance, if a data validation step fails, the pipeline might branch into an error-handling process, or if a task completes successfully, it moves to the next stage.

Decision-making ensures flexibility, efficiency, and error handling in automating complex workflows.

Notifications via email in pipelines are used to keep users informed about the progress and status of jobs or tasks.

Last updated 7 months ago