Improve current development documentation

[krisstern]

Describe your use-case which is not covered by existing documentation.

More details as well as contexts need to be provided for a better developer experience, such as what configurations are needed and how to start developing properly.

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

• https://tekton.dev/docs/getting-started/
• https://minikube.sigs.k8s.io/docs/start/

Are you interested in contributing to the documentation?

N/A

[kmsumanth23]

I think existing documentation lacks a clear step-by-step guide for integrating Tekton with Jenkins in environment like Docker Desktop and Minikube, so we can add some relevant documentation related to this.

[krisstern]

Yes, agreed

[kmsumanth23]

Thanks kris🙌!
So shall I raise a PR with a proper documentation for integration of Tekton with Jenkins?

[krisstern]

Yes, please go ahead with a pull request if you are interested in contributing.

[kmsumanth23]

I have also faced one more issue while setting up my Tekton environment i.e the missing UI fields (Credentials/Test Connection) while configuring the Tekton client in the system configuration settings.

I am using the latest version of Jenkins LTS.

so generally we have to set the credentials of our k8s cluster in Jenkins credential section (creating a secret credential by uploading the kubeconfig file to it and this credential is set to global scope so that we can use it anywhere in Jenkins ), after this,
we need to configure our Tekton pipelines client in the system configuration, in this section we need to fill out all the following to gain proper connection between Jenkins and our k8s cluster.

here are the following fields which are there in the latest version:

Name
unique identifier for the cluster

Master URL
kubernetes cluster where Tekton is running

Default Namespace
default namespace where Tekton resources should created

the below two fields are missing

Credentials

Test Connection

can you please check on this, because maybe I have made a mistake in setting up the environment or may be in the latest version there is no need to specify the credential, the Tekton pipeline directly fetches the global credentials.

[kmsumanth23]

Yes, please go ahead with a pull request if you are interested in contributing.

Thanks Kris, I will go ahead and create a proper documentation and raise a PR for the same🙌.