Skip to content

Commit 6c4491f

Browse files
committed
fix: polish docs on overriding steps locally
1 parent e99033d commit 6c4491f

File tree

2 files changed

+11
-2
lines changed

2 files changed

+11
-2
lines changed

content/en/v3/develop/pipelines/demo.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Demo
33
linktitle: Demo
44
type: docs
55
description: Demo of triggering and customising pipelines
6-
weight: 300
6+
weight: 150
77
---
88

99

content/en/v3/develop/pipelines/editing.md

+10-1
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,16 @@ e.g. for the default Jenkins X CI/CD pipelines edit either:
2929
* `release.yaml` to edit the Release [Task](https://tekton.dev/docs/pipelines/tasks/#configuring-a-task), [Pipeline](https://tekton.dev/docs/pipelines/pipelines/#configuring-a-pipeline) or [PipelineRun](https://tekton.dev/docs/pipelines/pipelineruns/#configuring-a-pipelinerun)
3030

3131
You can test out changes to the Pull Request pipeline by submitting changes in a Pull Request. Changes to a release only take place after merging the change to the main branch.
32-
32+
33+
### Overriding steps
34+
35+
The default pipelines use the default [Jenkins X Catalog](/v3/develop/pipelines/catalog/) and so the details of the steps such as the container image and commands used are often inherited.
36+
37+
You can override steps locally by:
38+
39+
* [Overriding a pipeilne step locally](/v3/develop/pipelines/catalog/#overriding-a-pipeline-step-locally) so that you inline the step details into your local YAML file and then edit accordingly.
40+
* [Override a specific step property locally such as the script property](/v3/develop/pipelines/catalog/#overriding-specific-properties-of-a-step-locally) which lets you just inline, say, the `script` commands to modify the commands run
41+
3342
### Tools
3443

3544
* [viewing the effective pipeline](/v3/develop/pipelines/catalog/#viewing-the-effective-pipeline)

0 commit comments

Comments
 (0)