changed references from concourse.ci to concourse-ci.org

Author: James Ma

artifactory-integration/README.md

@@ -83,8 +83,8 @@ This pipeline definition file can also be downloaded from [this repository](http
 
 ##### Pre-requisites
 
-1. An instance of [Concourse installed](http://concourse.ci/installing.html) up-and-running.  
-1. The [Concourse Fly command line interface](http://concourse.ci/fly-cli.html) installed on your local machine.  
+1. An instance of [Concourse installed](http://concourse-ci.org/installing.html) up-and-running.  
+1. The [Concourse Fly command line interface](http://concourse-ci.org/fly-cli.html) installed on your local machine.  
 1. A JFrog Artifactory server up-and-running.  
    For local tests, you can [run Artifactory as a Docker image](https://www.jfrog.com/confluence/display/RTF/Running+with+Docker).  
 

azure-blobstore-integration/README.md

@@ -92,8 +92,8 @@ jobs:
 
 ##### Pre-requisites
 
-1. An instance of [Concourse installed](http://concourse.ci/installing.html) up-and-running.  
-1. The [Concourse Fly command line interface](http://concourse.ci/fly-cli.html) installed on your local machine.  
+1. An instance of [Concourse installed](http://concourse-ci.org/installing.html) up-and-running.  
+1. The [Concourse Fly command line interface](http://concourse-ci.org/fly-cli.html) installed on your local machine.  
 1. An Azure Blobstore container setup.  
    In your Azure account, [create a blobstore storage account](https://docs.microsoft.com/en-us/azure/storage/storage-create-storage-account#create-a-storage-account). For example, for "Account kind", choose "Blob storage".  
    Then, create a container for the storage account. Choose the appropriate "Access type" that matches your needs (e.g. for "Private" and "Blob" you will have to provide your storage access key to the pipeline. I chose "Blob" for my tests). The name given to this container will be used in the pipeline definition file.

blue-green-app-deployment/README.md

@@ -41,11 +41,11 @@ For you to inspect which instance is being used by the main route, simply point
 The requirements for this pipeline's setup are as follows:
 
 1. An instance of Concourse installed either as a local vagrant machine or as a remote server.  
-   Please refer to the documentation on [how to install Concourse](http://concourse.ci/installing.html) or to article [Deploying Concourse on Bosh-lite](https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-on-bosh-lite).
+   Please refer to the documentation on [how to install Concourse](http://concourse-ci.org/installing.html) or to article [Deploying Concourse on Bosh-lite](https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-on-bosh-lite).
 
 1. The Concourse Fly command line interface is installed on the local VM.  
    The Fly cli can be downloaded directly from the link provided on the Concourse web interface.  
-   Please refer to the [Fly cli documentation](http://concourse.ci/fly-cli.html) for details.
+   Please refer to the [Fly cli documentation](http://concourse-ci.org/fly-cli.html) for details.
 
 
 ## Pipeline setup and execution

concourse-on-bosh-1.0/README.md

@@ -3,7 +3,7 @@
 
 # Concourse deployment with a Bosh 1.x manifest
 
-Concourse's [installation documentation](http://concourse.ci/clusters-with-bosh.html) provides only samples on how to install Concourse using a Bosh 2.0-style deployment manifests, i.e. manifests that rely on the Bosh 2.0 Cloud Config concept. In some instances though, customers may want to install Concourse on a new or existing Bosh Director where a Bosh 1.0 compliant deployment is in effect or desired for some reason.
+Concourse's [installation documentation](http://concourse-ci.org/clusters-with-bosh.html) provides only samples on how to install Concourse using a Bosh 2.0-style deployment manifests, i.e. manifests that rely on the Bosh 2.0 Cloud Config concept. In some instances though, customers may want to install Concourse on a new or existing Bosh Director where a Bosh 1.0 compliant deployment is in effect or desired for some reason.
 
 Having that said, this article provides sample steps on how to deploy Concourse 1.x on a Bosh Director not yet setup to use Cloud Config features. It also assumes that you have an instance of [Bosh Director](http://bosh.io/docs/init.html) already configured.
 
@@ -46,7 +46,7 @@ Having that said, this article provides sample steps on how to deploy Concourse
 
        ``external_url: http://XX.XX.XX.XX:8080```
 
-1. Deploy and run your pipelines as described in the [Concourse Documentation page](http://concourse.ci/fly-cli.html).
+1. Deploy and run your pipelines as described in the [Concourse Documentation page](http://concourse-ci.org/fly-cli.html).
 
 
 ---

concourse-on-bosh-lite/README.md

@@ -2,7 +2,7 @@
 
 # Deploying Concourse on Bosh-lite
 
-The quickest way to install and run a local copy of Concourse is by using the provided Vagrant image as mentioned in [Concourse’s documentation page](http://concourse.ci/vagrant.html). However, in certain cases, one may have the need to experiment with the Bosh-deployed version of Concourse in a local machine prior to moving it onto a shared/production environment later. For those cases, a solution is to install Concourse on top of a local Bosh-lite deployment. The section further below describes the steps to get that done.
+The quickest way to install and run a local copy of Concourse is by using the provided Vagrant image as mentioned in [Concourse’s documentation page](http://concourse-ci.org/vagrant.html). However, in certain cases, one may have the need to experiment with the Bosh-deployed version of Concourse in a local machine prior to moving it onto a shared/production environment later. For those cases, a solution is to install Concourse on top of a local Bosh-lite deployment. The section further below describes the steps to get that done.
 
 For more information about Bosh-lite and Concourse, please refer to the **Reference** section further below.
 
@@ -67,12 +67,12 @@ For more information about Bosh-lite and Concourse, please refer to the **Refere
 
        [http://10.244.8.2:8080/](http://10.244.8.2:8080/)
 
-11. Deploy and run your pipelines as described in the [Concourse Documentation page](http://concourse.ci/fly-cli.html).
+11. Deploy and run your pipelines as described in the [Concourse Documentation page](http://concourse-ci.org/fly-cli.html).
 
 
 ## References
 - Bosh-lite https://github.com/cloudfoundry/bosh-lite
-- Concourse http://concourse.ci/introduction.html
+- Concourse http://concourse-ci.org/introduction.html
 
 ## Credits
 Article based on deployment steps originally provided by Caleb Washburn

concourse-pipeline-hacks/check-resource/README.md

@@ -6,7 +6,7 @@
 
 After Concourse retrieves the latest version of a newly configured resource, it will not retrieve previous versions of that resource automatically anymore, even if those old versions are explicitly referred by the pipeline parameters.
 
-In order to force Concourse to retrieve an older version of a resource, use the fly CLI command with [`check-resource`](https://concourse.ci/fly-check-resource.html).
+In order to force Concourse to retrieve an older version of a resource, use the fly CLI command with [`check-resource`](https://concourse-ci.org/fly-check-resource.html).
 
 For example, in the sample pipeline further below, when you try to run job `unit-test` for the first time, it will get stuck waiting for Concourse to retrieve version `2.5.0` (an older version) of the `fly-release` resource while it shows the following message:
 ```

concourse-pipeline-hacks/docker-images-from-repo/README.md

@@ -26,8 +26,8 @@ Here is an example of a `rootfs` git repository with the required container file
 ![Rootfs-curl-repo](https://raw.githubusercontent.com/lsilvapvt/misc-support-files/master/docs/images/rootfs-curl-repo.jpg)
 
 
-To use that `rootfs` repository in a pipeline, use the  [`image`](https://concourse.ci/task-step.html#task-image) parameter instead of `image_resource` when defining a task.  
-For defining [resource types](https://concourse.ci/configuring-resource-types.html) using `rootfs` repositories, use `type: git` instead of `type: docker-image` in the `resource_types` entries of the pipeline.
+To use that `rootfs` repository in a pipeline, use the  [`image`](https://concourse-ci.org/task-step.html#task-image) parameter instead of `image_resource` when defining a task.  
+For defining [resource types](https://concourse-ci.org/configuring-resource-types.html) using `rootfs` repositories, use `type: git` instead of `type: docker-image` in the `resource_types` entries of the pipeline.
 
 ### Sample pipeline
 
@@ -105,6 +105,6 @@ The techniques described here should only be used for temporary Concourse demons
 
 - [Running tasks with Docker images from an S3 bucket]( https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-pipeline-hacks/docker-images-from-s3)
 
-- [Concourse documentation on running tasks with a rootfs image]( https://concourse.ci/running-tasks.html#task-config-image)
+- [Concourse documentation on running tasks with a rootfs image]( https://concourse-ci.org/running-tasks.html#task-config-image)
 
 #### [Back to Concourse Pipeline Hacks](..)

concourse-pipeline-hacks/docker-images-from-s3/README.md

@@ -94,7 +94,7 @@ Another example of such download-and-package pipeline is also available from [th
 
 ### See also
 
-- [Concourse documentation on running tasks with a rootfs image]( https://concourse.ci/running-tasks.html#task-config-image)
+- [Concourse documentation on running tasks with a rootfs image]( https://concourse-ci.org/running-tasks.html#task-config-image)
 
 - [Running pipeline tasks and resources without a Docker registry](https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-pipeline-hacks/docker-images-from-repo)
 

concourse-pipeline-hacks/task-run-user/README.md

@@ -8,7 +8,7 @@ Of course, this will not work for you if one of your task's image/container requ
 
 ### The solution
 
-To accommodate that requirement, Concourse provides a [`user` parameter](http://concourse.ci/running-tasks.html#task-run-user) for you to explicitly set the user to run a task container with.
+To accommodate that requirement, Concourse provides a [`user` parameter](http://concourse-ci.org/running-tasks.html#task-run-user) for you to explicitly set the user to run a task container with.
 
 
 #### Sample pipeline

concourse-pipeline-patterns/gated-pipelines/01-simple/README.md

@@ -1,7 +1,7 @@
 # A simple gated CI pipeline
 
 In Concourse, a job requires to be manually triggered by default, as long as none of
-its resources specify the "[trigger: true](http://concourse.ci/get-step.html#trigger)" parameter.
+its resources specify the "[trigger: true](http://concourse-ci.org/get-step.html#trigger)" parameter.
 
 Therefore, in order to create a "gated" step in a pipeline, a simple job that requires a manual trigger needs to be inserted into it.
 

concourse-pipeline-patterns/parameterized-pipeline-tasks/README.md

@@ -9,12 +9,12 @@ That allows for the reuse of common task definitions, for example, `package rele
 
 ### Key-value pairs with `params`
 
-Key-value pairs can be passed to a task through a [`params`](http://concourse.ci/running-tasks.html#params) section in the task definition. Each `key` entry will become an **environment variable** during the execution of the task.
+Key-value pairs can be passed to a task through a [`params`](http://concourse-ci.org/running-tasks.html#params) section in the task definition. Each `key` entry will become an **environment variable** during the execution of the task.
 
 
 ### Input and Output Mappings
 
-The `inputs` and `outputs` of a task can be parameterized with [input-mappings](http://concourse.ci/task-step.html#input_mapping) and [output-mappings](http://concourse.ci/task-step.html#output_mapping) respectively.  
+The `inputs` and `outputs` of a task can be parameterized with [input-mappings](http://concourse-ci.org/task-step.html#input_mapping) and [output-mappings](http://concourse-ci.org/task-step.html#output_mapping) respectively.  
 That means that an entire input or output folder that is expected by the task (e.g. a github release or S3) can be "substituted" with another folder from a pipeline resource for each run of the task.
 
 

concourse-pipeline-patterns/uaa-authentication/README.md

@@ -7,7 +7,7 @@
 
 # Authenticating Concourse team members with PCF UAA
 
-Concourse can be [integrated with a Cloud Foundry UAA server](http://concourse.ci/teams.html#uaa-cf-auth) to authenticate and authorize members of a specific team based on CF Organization/Space membership.
+Concourse can be [integrated with a Cloud Foundry UAA server](http://concourse-ci.org/teams.html#uaa-cf-auth) to authenticate and authorize members of a specific team based on CF Organization/Space membership.
 
 The authorization of the users for a Concourse team is validated against the user membership of a specific `space` in Cloud Foundry.
 
@@ -55,7 +55,7 @@ uaac client add concourse \
 
 #### 2. Configure a Concourse team that delegates authentication to UAA
 
-From a machine that can connect to Concourse via [FLY cli](http://concourse.ci/fly-cli.html), set the Concourse team with UAA authentication:
+From a machine that can connect to Concourse via [FLY cli](http://concourse-ci.org/fly-cli.html), set the Concourse team with UAA authentication:
 
 ```
 fly -t <your-target> set-team -n <team-name> \

concourse-pipeline-patterns/vault-integration/README.md

@@ -2,7 +2,7 @@
 
 # How to integrate Concourse pipelines with Vault
 
-Concourse 3.3.1+ supports [credential management integration with HashiCorp's Vault](http://concourse.ci/creds.html) and eliminates the need to feed credentials to pipelines via plain-text parameter files.  
+Concourse 3.3.1+ supports [credential management integration with HashiCorp's Vault](http://concourse-ci.org/creds.html) and eliminates the need to feed credentials to pipelines via plain-text parameter files.  
 
 This integration requires configuration updates to both Vault and Concourse servers as described further below.
 
@@ -19,7 +19,7 @@ jobs:
       SYS_USERNAME: ((vault-system-username))
 ```
 
-When Concourse runs that pipeline/job, it will search for the corresponding secret in Vault, using a [pre-determined search order](http://concourse.ci/creds.html#vault), and execute the task appropriately with the retrieved values.
+When Concourse runs that pipeline/job, it will search for the corresponding secret in Vault, using a [pre-determined search order](http://concourse-ci.org/creds.html#vault), and execute the task appropriately with the retrieved values.
 
 
 ## Configuring the Vault server
@@ -63,7 +63,7 @@ On an [unsealed](https://www.vaultproject.io/docs/concepts/seal.html) Vault serv
 
 Copy the token value from the step further above and set it in the Concourse server.
 
-* For binary-based Concourse deployments, see [the Concourse documentation](http://concourse.ci/creds.html) for setup instructions.
+* For binary-based Concourse deployments, see [the Concourse documentation](http://concourse-ci.org/creds.html) for setup instructions.
 
 * For Bosh-based Concourse deployments, update the `atc` job properties in the deployment manifest as described below and then redeploy Concourse:
 
@@ -88,7 +88,7 @@ For a complete list of Vault integration parameters for the `atc` job, please co
 
 Then, once you run the pipelines, you should see secret keys being replaced with the corresponding values retrieved from the Vault server by Concourse.
 
-For more information on Concourse and Vault integration, please refer to Concourse's [Credentials Management documentation page](http://concourse.ci/creds.html).
+For more information on Concourse and Vault integration, please refer to Concourse's [Credentials Management documentation page](http://concourse-ci.org/creds.html).
 
 
 ### Hint: how to keep pipeline YML files untouched and still integrate with Vault

email-with-attachments/README.md

@@ -49,8 +49,8 @@ If you want to see the full sample pipeline provided in action, here is how you
 
 ##### Pre-requisites to setup this example on your Concourse server
 
-1. An instance of [Concourse installed](http://concourse.ci/installing.html) up-and-running.  
-1. The [Concourse Fly command line interface](http://concourse.ci/fly-cli.html) installed on your local machine.
+1. An instance of [Concourse installed](http://concourse-ci.org/installing.html) up-and-running.  
+1. The [Concourse Fly command line interface](http://concourse-ci.org/fly-cli.html) installed on your local machine.
 
 ##### Configuration steps
 1. Clone the sample git repository on your local machine  

google-cloud-storage-integration/README.md

@@ -105,8 +105,8 @@ jobs:
 
 ##### Pre-requisites
 
-1. An instance of [Concourse installed](http://concourse.ci/installing.html) up-and-running.  
-1. The [Concourse Fly command line interface](http://concourse.ci/fly-cli.html) installed on your local machine.  
+1. An instance of [Concourse installed](http://concourse-ci.org/installing.html) up-and-running.  
+1. The [Concourse Fly command line interface](http://concourse-ci.org/fly-cli.html) installed on your local machine.  
 1. A Google Cloud Storage bucket setup  
    To create one:  
    - go to your [GCP account dashboard](https://console.cloud.google.com/home/dashboard);  

pcf-cfops-backup/README.md

@@ -67,12 +67,12 @@ In the "CleanUp" tab of the pipeline, a single job is defined to perform a night
 The requirements for this pipeline's setup are as follows:
 
 1. An instance of Concourse installed either as a local vagrant machine or as a remote server.  
-   Please refer to the documentation on [how to install Concourse](http://concourse.ci/installing.html) or to article [Deploying Concourse on Bosh-lite](https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-on-bosh-lite).  
+   Please refer to the documentation on [how to install Concourse](http://concourse-ci.org/installing.html) or to article [Deploying Concourse on Bosh-lite](https://github.com/pivotalservices/concourse-pipeline-samples/tree/master/concourse-on-bosh-lite).  
    Note that the size of backup files produced by CFOps for some PCF components may be of 10+ Gigabytes each, so plan to have large disk sizes in place for the Concourse Worker VMs in order to avoid build failures due to not enough available disk space.
 
 1. The Concourse Fly command line interface is installed on the local VM.  
    The Fly cli can be downloaded directly from the link provided on the Concourse web interface.  
-   Please refer to the [Fly cli documentation](http://concourse.ci/fly-cli.html) for details.
+   Please refer to the [Fly cli documentation](http://concourse-ci.org/fly-cli.html) for details.
 
 1. A deployed instance of PCF that is managed by an Ops Manager