mirror of https://github.com/kubeflow/website.git
30 lines
1.4 KiB
Markdown
30 lines
1.4 KiB
Markdown
+++
|
|
title = "Run and Recurring Run"
|
|
description = "Conceptual overview of runs in Kubeflow Pipelines"
|
|
weight = 50
|
|
+++
|
|
|
|
A *run* is a single execution of a pipeline. Runs comprise an immutable log of
|
|
all experiments that you attempt, and are designed to be self-contained to allow
|
|
for reproducibility. You can track the progress of a run by looking at its
|
|
details page on the Kubeflow Pipelines UI, where you can see the runtime graph,
|
|
output artifacts, and logs for each step in the run.
|
|
|
|
<a id=recurring-run>
|
|
A *recurring run* is a repeatable run of a pipeline. The
|
|
configuration for a recurring run includes a copy of a pipeline with all
|
|
parameter values specified and a
|
|
[run trigger](/docs/pipelines/concepts/run-trigger/).
|
|
You can start a recurring run inside any experiment, and it will periodically
|
|
start a new copy of the run configuration. You can enable/disable the recurring
|
|
run from the Kubeflow Pipelines UI. You can also specify the maximum number of
|
|
concurrent runs, to limit the number of runs launched in parallel. This can be
|
|
helpful if the pipeline is expected to run for a long period of time and is
|
|
triggered to run frequently.
|
|
|
|
## Next steps
|
|
|
|
* Read an [overview of Kubeflow Pipelines](/docs/pipelines/pipelines-overview/).
|
|
* Follow the [pipelines quickstart guide](/docs/pipelines/pipelines-quickstart/)
|
|
to deploy Kubeflow and run a sample pipeline directly from the Kubeflow
|
|
Pipelines UI. |