github.com/pachyderm/pachyderm@v1.13.4/doc/docs/1.10.x/how-tos/run_pipeline.md (about) 1 # Run a Pipeline on a Specific Commit 2 3 Sometimes you need to see the result of merging different commits 4 to analyze and identify correct combinations and potential flows in 5 data collection and processing. Or, you just want to rerun a failed job 6 manually. 7 8 Pachyderm enables you to run your pipelines with old commits or in different 9 handpicked combinations of old commits that are stored in separate 10 repositories or branches. This functionality is particularly useful for 11 cross-pipelines, but you can also use it with other types of pipelines. 12 13 For example, you have branches `A`, `B`, and `C`. Each of these branches has 14 had commits on it at various times, and each new commit 15 triggered a new job from the pipeline. 16 17 Your branches have the following commit history: 18 19 * Branch `A` has commits `A1`, `A2`, `A3`, and `A4`. 20 * Branch `B` has commits `B1` and `B2`. 21 * Branch `C` has commits `C1`, `C2`, and `C3`. 22 23 For example, you need to see the result of the 24 pipeline with the combination of data after `A4`, `B1`, and `C2` were 25 committed. 26 But none of the output commits were triggered on this particular combination. 27 28 To get the result of this combination, you can run the `pachctl run pipeline 29 cross-pipe` command. 30 31 !!! example 32 ```shell 33 pachctl run pipeline cross-pipe A4 B1 C2 34 ``` 35 36 This command triggers a new job that creates a commit on the 37 pipeline's output branch with the result of that combination of data. 38 39 Because `A4` is the head of branch `A`, you can also omit the `A4` commit 40 in the command and specify only the `C2` and `B1` commits: 41 42 !!! example 43 ``` 44 pachctl run pipeline cross-pipe C2 B1 45 ``` 46 47 Pachyderm automatically uses the head for any branch that did not have a 48 commit specified. The order in which you specify the commits does not 49 matter. Pachyderm knows how to match them to the right place. 50 51 Also, you can reference the head commit of a branch by using the branch 52 name. 53 54 !!! example 55 56 ```shell 57 pachctl run pipeline cross-pipe A B1 C2 58 ``` 59 60 This behavior implies that if you want to re-run the pipeline on the 61 most recent commits, you can just run `pachctl run pipeline cross-pipe`. 62 63 If you try to use a commit from a branch that is not an input 64 branch, `pachctl` returns an error. 65 Similarly, specifying multiple commits from the same branch results in error. 66 67 You do not need to run the `pachctl run pipeline cross-pipe` 68 command to initiate a newly created pipeline. Pachyderm runs the new 69 pipelines automatically as you add new commits to the corresponding 70 input branches.