From 22a4a267fdeaae481261c1b68b66921a425caad2 Mon Sep 17 00:00:00 2001 From: Bruno Bandeira de Azevedo Date: Mon, 25 Jun 2018 17:12:58 +0200 Subject: [PATCH] Fix on Readme for Concourse links --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 61c65ec..92460fe 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ resource only support *GITHUB*. ## Deploying to Concourse -You can use the docker image by defining the [resource type](http://concourse.ci/configuring-resource-types.html) in your pipeline YAML. +You can use the docker image by defining the [resource type](https://concourse-ci.org/resource-types.html) in your pipeline YAML. For example: @@ -41,7 +41,7 @@ resource_types: linking to builds. On newer versions of Concourse ( >= v0.71.0) , the resource will automatically sets the URL. - This supports the [build environment](http://concourse.ci/implementing-resources.html#resource-metadata) + This supports the [build environment](https://concourse-ci.org/implementing-resources.html#resource-metadata) variables provided by concourse. For example, `context: $BUILD_JOB_NAME` will set the context to the job name. * `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. * `path`: *Required.* The path of the repository to reference the pull request. * `status`: *Required.* The status of success, failure, error, or pending. - * [`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). + * [`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). * `context`: *Optional.* The context on the specified pull request (defaults to `status`). Any context will be prepended with `concourse-ci`, so a context of `unit-tests` will appear as `concourse-ci/unit-tests` on Github. - This supports the [build environment](http://concourse.ci/implementing-resources.html#resource-metadata) + This supports the [build environment](https://concourse-ci.org/implementing-resources.html#resource-metadata) variables provided by concourse. For example, `context: $BUILD_JOB_NAME` will set the context to the job name. * `comment`: *Optional.* The file path of the comment message. Comment owner is same with the owner of `access_token`.