@@ -19,54 +19,62 @@ There is a few things you can configure through the config map
1919 application to be used with private repositories. This feature is enabled by
2020 default.
2121
22- * ` secret-github-app-token-scopped `
22+ * ` secret-github-app-token-scoped `
2323
24- When using a Github app, we generate a temporary installation token, we scope it
25- to the repository from where the payload comes. We do this when the Github app
26- is configured globally on a Github organization.
24+ When using a Github app, ` Pipelines as Code ` will generate a temporary
25+ installation token for every allowed event coming through the controller.
2726
28- If the organization has a mix of public and private repositories and not every
29- user in the organization is trusted to have access to every repository, then the
30- scoped token would not allow them to access those .
27+ The generated token will be scoped to the repository from the repository where
28+ the payload come from and not to every repositories the app installation has
29+ access to .
3130
32- If you trust every user on your organization to access any repository or you are
33- not planning to install your Github app globally on a Github organization, then
34- you can safely set this option to false.
31+ Having access to every repositories the app has access to is a problem when
32+ you install the ` Pipelines as Code ` application into an organization that has
33+ a mixed between public and private repositories where every users in the
34+ organization is not trusted to have access to the private repositores. Since
35+ the scoping of the token only allow the user do operations and access on the
36+ repository where the payload come from, it will not be able to access the private repos.
37+
38+ However, if you trust every users of your organization to access any repositories or
39+ you are not planning to install your GitHub app globally on a GitHub
40+ organization, then you can safely set this option to false.
3541
3642* ` secret-github-app-scope-extra-repos `
3743
38- If you don't want to completely disable the scopping of the token, but still
39- wants some other repos available, then you can add an extra owner/repo here.
44+ If you don't want to completely disable the scoping of the token, but still
45+ wants some other repos available (as long you have installed the github app on
46+ it), then you can add an extra owner/repo here.
4047
4148 This let you able fetch remote url on github from extra private repositories
4249 in an organisation if you need it.
4350
4451 This only works when all the repos are added from the same installation IDs.
45-
52+
4653 You can have multiple owner/repository separated by commas:
47-
54+
4855 ``` yaml
49- secret-github-app-token-scopped : " owner/private-repo1, org/repo2"
56+ secret-github-app-token-scoped : " owner/private-repo1, org/repo2"
5057 ` ` `
5158
5259* ` remote-tasks`
5360
54- Let allows remote tasks from pipelinerun annotations. This feature is enabled by
55- default.
61+ This allows fetching remote tasks on pipelinerun annotations. This feature is
62+ enabled by default.
5663
5764* `hub-url`
5865
5966 The base URL for the [tekton hub](https://github.com/tektoncd/hub/)
60- API. default to the [public hub](https://hub.tekton.dev/) : <https://api.hub.tekton.dev/v1>
67+ API. This default to the [public hub](https://hub.tekton.dev/) : <https://api.hub.tekton.dev/v1>
6168
6269* `hub-catalog-name`
6370
64- The [tekton hub](https://github.com/tektoncd/hub/) catalog name. default to tekton
71+ The [tekton hub](https://github.com/tektoncd/hub/) catalog name. default to ` tekton`
6572
6673* `tekton-dashboard-url`
6774
68- Using the URL of the Tekton dashboard, Pipelines-as-Code generates a URL to the PipelineRun on the Tekton dashboard.
69- If you are an OpenShift user, then OpenShift console URL is auto-detected.
75+ When you are not running on Openshift using the [tekton
76+ dashboard](https://github.com/tektoncd/dashboard/) you will need to specify a
77+ dashboard url to have the logs tnd the pipelinerun details linked.
7078
7179* `bitbucket-cloud-check-source-ip`
7280
@@ -83,69 +91,127 @@ There is a few things you can configure through the config map
8391
8492* `bitbucket-cloud-additional-source-ip`
8593
86- This will provide us to give extra IPS (ie : 127.0.0.1) or networks (127.0.0.0/16)
94+ Let you add extra IPS to allow bitbucket clouds, you can do a specific IP :
95+ ` 127.0.0.1` or a networks `127.0.0.0/16`. Multile of them can be specified
8796 separated by commas.
8897
8998* `max-keep-run-upper-limit`
9099
91- This let the user define a max limit for the max-keep-run value. When the user has defined a max-keep-run annotation
92- on a pipelineRun then its value should be less than or equal to the upper limit, otherwise upper limit will be used for cleanup.
100+ This let the user define a max limit for the max-keep-run value. When the user
101+ has defined a max-keep-run annotation on a pipelineRun then its value should
102+ be less than or equal to the upper limit, otherwise upper limit will be used
103+ for cleanup.
93104
94105* `default-max-keep-runs`
95106
96- This allows user to define a default limit for max-keep-run value. If defined then it's applied to all the pipelineRun
97- which do not have `max-keep-runs` annotation.
107+ This let the user define a default limit for the `max-keep-run` value.
108+ When defined it will applied to all the pipelineRun without a `max-keep-runs`
109+ annotation.
98110
99111* `auto-configure-new-github-repo`
100112
101- This setting let you autoconfigure newly created GitHub repositories. On creation of a new repository, Pipelines As Code will set up a namespace
102- for your repository and create a Repository CR.
113+ This setting let you autoconfigure newly created GitHub repositories. When
114+ Pipelines as Code sees a new repository URL from a payload, It Code will set
115+ up a namespace for your repository and create a Repository CR.
103116
104117 This feature is disabled by default and is only supported with GitHub App.
105118
106- {< hint info >}
107- If you have a GitHub App already setup then verify if `Repository` event is subscribed.
108- {< /hint >}
119+ {{< hint info >}}
120+ If you have a GitHub App already setup then verify if the `repository` event is
121+ subscribed into your Github App setting.
122+ {{< /hint >}}
109123
110124* `auto-configure-repo-namespace-template`
111125
112- If `auto-configure-new-github-repo` is enabled then you can provide a template for generating the namespace for your new repository.
113- By default, the namespace will be generated using this format `{{repo_name}}-pipelines`.
126+ If `auto-configure-new-github-repo` is enabled then you can provide a template
127+ for generating the namespace for your new repository. By default, the
128+ namespace will be generated using this format `{{repo_name}}-pipelines`.
114129
115130 You can override the default using the following variables
116131
117132 * `{{repo_owner}}`: The repository owner.
118133 * `{{repo_name}}`: The repository name.
119134
120- for example. if the template is defined as `{{repo_owner}}-{{repo_name}}-ci`, then the namespace generated for repository
135+ For example. if the template is defined as `{{repo_owner}}-{{repo_name}}-ci`,
136+ then the namespace generated for repository
137+
121138 ` https://github.com/owner/repo` will be `owner-repo-ci`
122139
123140* `error-log-snippet`
124141
125- Enable or disable the feature to show a log snippet of the failed task when there is
126- an error in a Pipeline
142+ Enable or disable the feature to show a log snippet of the failed task when
143+ there is an error in a PipelineRun.
144+
145+ Due of the constraint of the different GIT provider API, It will show the last
146+ 3 lines of the first container from the first task that has exited with an
147+ error in the PipelineRun.
148+
149+ If it find any strings matching the values of secrets attached to the
150+ PipelineRun it will replace it with the placeholder `******`
151+
152+ * `error-log-snippet`
153+
154+ {{ hint danger }}
155+ alpha feature : may change at any time
156+ {{ /hint danger }}
157+
158+ Enable or disable the inspection of container logs to detect error message
159+ and expose them as annotations on Pull Request. Only Github apps is supported.
127160
128- It will show the last 3 lines of the first container of the first task
129- that has error in the pipeline.
161+ * `error-detection-max-number-of-lines`
130162
131- If it find any strings matching the values of secrets attached to the PipelineRun it will replace it with the placeholder `******`
163+ {{ hint danger }}
164+ alpha feature : may change at any time
165+ {{ /hint danger }}
166+
167+ How many lines to grab from the container when inspecting the
168+ logs for error detection when using `error-log-snippet`. Increasing this value
169+ may increase the watcher memory usage. The default is 50, increase this value
170+ or use -1 for unlimited.
171+
172+ * `error-detection-simple-regexp`
173+
174+ {{ hint danger }}
175+ alpha feature : may change at any time
176+ {{ /hint danger }}
177+
178+ By default error detection only support the simple outputs, the way GCC or
179+ make will output which is supported by most linters and command line tools.
180+
181+ An example is :
182+
183+ ` ` ` console
184+ test.js:100:10: an error occurred
185+ ` ` `
186+
187+ Pipelines as Code will see this line and show it as an annotation on the pull
188+ request where the error occurred.
189+
190+ You can configure the default regexp used for detection. You will need to
191+ keep the regexp groups : ` <filename>` , `<line>`, `<error>` to make it works.
132192
133193# # Pipelines-As-Code Info
134194
135- There are a settings exposed through a config map which any authenticated user can access to know about
136- Pipeline as Code.
195+ There are a settings exposed through a config map for which any authenticated
196+ user can access to know about the Pipeline as Code status .
137197
138198* `version`
139199
140- The version of Pipelines As Code installed.
200+ The version of Pipelines As Code currently installed.
141201
142202* `controller-url`
143203
144- The controller URL as set by the `tkn pac bootstrap` command while setting up the GitHub App or if Pipelines as code is installed
145- using OpenShift Pipelines Operator then the operator sets the route created for the controller. This field is also used to detect the controller
146- URL in `webhook add` commands.
204+ The controller URL as set by the `tkn pac bootstrap` command while setting up
205+ the GitHub App or if Pipelines as code is installed
206+
207+ When using OpenShift Pipelines Operator then the operator sets the route created
208+ for the controller.
209+
210+ This field is also used to detect the controller URL when using the `webhook add`
211+ commands.
147212
148213* `provider`
149214
150- The provider is set to `GitHub App` by tkn pac bootstrap command and is used to detect if a GitHub App is already configured when a user runs the
151- bootstrap command a second time or the `webhook add` command.
215+ The provider set to `GitHub App` by tkn pac bootstrap, used to detect if a
216+ GitHub App is already configured when a user runs the bootstrap command a
217+ second time or the `webhook add` command.
0 commit comments