Skip to content

Commit 428e961

Browse files
committed
RHDEVDOCS-3903: Added a note related to add tasks from your local tekton hub instance
1 parent f4a6465 commit 428e961

File tree

2 files changed

+14
-1
lines changed

2 files changed

+14
-1
lines changed

cicd/pipelines/working-with-pipelines-using-the-developer-perspective.adoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ include::modules/op-constructing-pipelines-using-pipeline-builder.adoc[leveloffs
2929

3030
== Creating OpenShift Pipelines along with applications
3131

32-
To create pipelines along with applications, use the *From Git* option in the *Add+* view of the *Developer* perspective. You can view all of your available pipelines and select the pipelines you want to use to create applications while importing your code or deploying an image.
32+
To create pipelines along with applications, use the *From Git* option in the *Add+* view of the *Developer* perspective. You can view all of your available pipelines and select the pipelines you want to use to create applications while importing your code or deploying an image.
3333

3434
The Tekton Hub Integration is enabled by default and you can see tasks from the Tekton Hub that are supported by your cluster. Administrators can opt out of the Tekton Hub Integration and the Tekton Hub tasks will no longer be displayed. You can also check whether a webhook URL exists for a generated pipeline. Default webhooks are added for the pipelines that are created using the *+Add* flow and the URL is visible in the side panel of the selected resources in the Topology view.
3535

@@ -48,3 +48,9 @@ include::modules/op-interacting-pipelines-from-topology-view.adoc[leveloffset=+1
4848
include::modules/op-editing-pipelines.adoc[leveloffset=+1]
4949

5050
include::modules/op-deleting-pipelines.adoc[leveloffset=+1]
51+
52+
[role="_additional-resources"]
53+
[id="additional-resources-working-with-pipelines-using-the-developer-perspective"]
54+
== Additional resources
55+
56+
* xref:../../cicd/pipelines/using-tekton-hub-with-openshift-pipelines.adoc#using-tekton-hub-with-openshift-pipelines[Using Tekton Hub with OpenShift Pipelines]

modules/op-constructing-pipelines-using-pipeline-builder.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,13 @@ In the *Developer* perspective of the console, you can use the *+Add* -> *Pipeli
1515
* Reference these pipeline resources in each of the tasks in the pipeline as input and output resources.
1616
* If required, reference any additional parameters added to the pipeline in the task. The parameters for a task are prepopulated based on the specifications of the task.
1717
* Use the Operator-installed, reusable snippets and samples to create detailed pipelines.
18+
* Search and add tasks from your configured local Tekton Hub instance.
19+
20+
[IMPORTANT]
21+
====
22+
In the developer perspective, you can create a customized pipeline using your own set of curated tasks. To search, install, and upgrade your tasks directly from the developer console, your cluster administrator needs to install and deploy a local Tekton Hub instance and link that hub to the OpenShift Container Platform cluster. For more details, see _Using Tekton Hub with OpenShift Pipelines_ in the _Additional resources_ section.
23+
If you do not deploy any local Tekton Hub instance, by default, you can only access the cluster tasks, namespace tasks and public Tekton Hub tasks.
24+
====
1825

1926
.Procedure
2027

0 commit comments

Comments
 (0)