You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ resource only support *GITHUB*.
9
9
10
10
## Deploying to Concourse
11
11
12
-
You can use the docker image by defining the [resource type](http://concourse.ci/configuring-resource-types.html) in your pipeline YAML.
12
+
You can use the docker image by defining the [resource type](https://concourse-ci.org/resource-types.html) in your pipeline YAML.
13
13
14
14
For example:
15
15
@@ -41,7 +41,7 @@ resource_types:
41
41
linking to builds. On newer versions of Concourse ( >= v0.71.0) , the resource will
42
42
automatically sets the URL.
43
43
44
-
This supports the [build environment](http://concourse.ci/implementing-resources.html#resource-metadata)
44
+
This supports the [build environment](https://concourse-ci.org/implementing-resources.html#resource-metadata)
45
45
variables provided by concourse. For example, `context: $BUILD_JOB_NAME` will set the context to the job name.
46
46
47
47
* `private_key`: *Optional.* Private key to use when pulling/pushing.
@@ -170,13 +170,13 @@ Set the status message for `concourse-ci` context on specified pull request.
170
170
* `path`: *Required.* The path of the repository to reference the pull request.
171
171
172
172
* `status`: *Required.* The status of success, failure, error, or pending.
173
-
* [`on_success`](https://concourse.ci/on-success-step.html) and [`on_failure`](https://concourse.ci/on-failure-step.html) triggers may be useful for you when you wanted to reflect build result to the PR (see the example below).
173
+
* [`on_success`](https://concourse-ci.org/on-success-step-hook.html#on_success) and [`on_failure`](https://concourse-ci.org/on-failure-step-hook.html#on_failure) triggers may be useful for you when you wanted to reflect build result to the PR (see the example below).
174
174
175
175
* `context`: *Optional.* The context on the specified pull request
176
176
(defaults to `status`). Any context will be prepended with `concourse-ci`, so
177
177
a context of `unit-tests` will appear as `concourse-ci/unit-tests` on Github.
178
178
179
-
This supports the [build environment](http://concourse.ci/implementing-resources.html#resource-metadata)
179
+
This supports the [build environment](https://concourse-ci.org/implementing-resources.html#resource-metadata)
180
180
variables provided by concourse. For example, `context: $BUILD_JOB_NAME` will set the context to the job name.
181
181
182
182
* `comment`: *Optional.* The file path of the comment message. Comment owner is same with the owner of `access_token`.
0 commit comments