update to new concourse domain

atom-extensions/atom-concourse/README.md

@@ -2,7 +2,7 @@
 [![macOS Build Status](https://travis-ci.org/spring-projects/atom-concourse.svg?branch=master)](https://travis-ci.org/spring-projects/atom-concourse) [![Windows Build Status](https://ci.appveyor.com/api/projects/status/1jvknxt9jhykgrxo?svg=true)](https://ci.appveyor.com/project/spring-projects/atom-concourse/branch/master) [![Dependency Status](https://david-dm.org/spring-projects/atom-concourse.svg)](https://david-dm.org/spring-projects/atom-concourse)
 
 This extension provides basic validation, content assist and hover infos
-for editing Concourse [Pipeline](https://concourse.ci/pipelines.html) and [Task Configuration](https://concourse.ci/running-tasks.html) Files.
+for editing Concourse [Pipeline](https://concourse-ci.org/pipelines.html) and [Task Configuration](https://concourse-ci.org/running-tasks.html) Files.
 
 It is recommended to use this extension package when `atom-ide-ui` atom extension package is installed. Thus, reconciling (error/warning markers) and hover support is fully functional. 
 

headless-services/concourse-language-server/src/main/resources/desc/GetStep/get.md

@@ -17,5 +17,5 @@ plan:
 get: string
 ```
 
-*Required.* The logical name of the resource being fetched. This name satisfies logical inputs to a [Task](https://concourse.ci/concepts.html#tasks), and may be referenced within the plan itself (e.g. in the `file` attribute of a `task` step).
+*Required.* The logical name of the resource being fetched. This name satisfies logical inputs to a [Task](https://concourse-ci.org/concepts.html#tasks), and may be referenced within the plan itself (e.g. in the `file` attribute of a `task` step).
 

headless-services/concourse-language-server/src/main/resources/desc/GitSource/ignore_paths.md

@@ -3,8 +3,8 @@ to the specified files are ignored.
 
 Note that if you want to push commits that change these files via a `put`,
 the commit will still be "detected", as [`check` and `put` both introduce
-versions](https://concourse.ci/pipeline-mechanics.html#collecting-versions).
+versions](https://concourse-ci.org/pipeline-mechanics.html#collecting-versions).
 To avoid this you should define a second resource that you use for commits
 that change files that you don't want to feed back into your pipeline - think
 of one as read-only (with `ignore_paths`) and one as write-only (which
-shouldn't need it).
+shouldn't need it).

headless-services/concourse-language-server/src/main/resources/desc/GitSource/password.md

@@ -1,3 +1,3 @@
 *Optional.* Password for HTTP(S) auth when pulling/pushing.
 
-Note: You can also use pipeline templating to hide this password in source control. (For more information: https://concourse.ci/fly-set-pipeline.html)
+Note: You can also use pipeline templating to hide this password in source control. (For more information: https://concourse-ci.org/fly-set-pipeline.html)

headless-services/concourse-language-server/src/main/resources/desc/GitSource/private_key.md

@@ -9,4 +9,4 @@ Example:
 	    DWiJL+OFeg9kawcUL6hQ8JeXPhlImG6RTUffma9+iGQyyBMCGd1l
 	    -----END RSA PRIVATE KEY-----
 
-Note: You can also use pipeline templating to hide this private key in source control. (For more information: https://concourse.ci/fly-set-pipeline.html)
+Note: You can also use pipeline templating to hide this private key in source control. (For more information: https://concourse-ci.org/fly-set-pipeline.html)

headless-services/concourse-language-server/src/main/resources/desc/Pipeline/groups.md

@@ -17,5 +17,5 @@ A simple grouping for the pipeline above may look like:
 
 This would display two tabs at the top of the home page: "tests" and "deploy". Once you have added groups to your pipeline then all jobs must be in a group otherwise they will not be visible.
 
-For a real world example of how groups can be used to simplify navigation and provide logical grouping, see the groups used at the top of the page in the [Concourse pipeline](https://ci.concourse.ci/).
+For a real world example of how groups can be used to simplify navigation and provide logical grouping, see the groups used at the top of the page in the [Concourse pipeline](https://ci.concourse-ci.org/).
 

headless-services/concourse-language-server/src/main/resources/desc/PutStep/put.md

@@ -1,7 +1,7 @@
-Pushes to the given [Resource](https://concourse.ci/concepts.html#resources). 
+Pushes to the given [Resource](https://concourse-ci.org/concepts.html#resources). 
 All artifacts collected during the plan's execution will be available in the working directory.
 
-For example, the following plan fetches a repo using [get](https://concourse.ci/get-step.html) and pushes it to another repo (assuming `repo-develop` and `repo-master` are defined as `git` resources):
+For example, the following plan fetches a repo using [get](https://concourse-ci.org/get-step.html) and pushes it to another repo (assuming `repo-develop` and `repo-master` are defined as `git` resources):
 
 ```
 plan:
@@ -34,4 +34,4 @@ plan:
 put: string
 ```
 
-Required. The logical name of the resource being pushed. The pushed resource will be available under this name after the push succeeds.
+Required. The logical name of the resource being pushed. The pushed resource will be available under this name after the push succeeds.

headless-services/concourse-language-server/src/main/resources/desc/PutStep/resource.md

@@ -1,3 +1,3 @@
 *Optional.* Defaults to `name`.
 
-The resource to update, as configured in [resources](https://concourse.ci/configuring-resources.html).
+The resource to update, as configured in [resources](https://concourse-ci.org/configuring-resources.html).

headless-services/concourse-language-server/src/main/resources/desc/Resource/name.md

@@ -1 +1 @@
-*Required.* The name of the resource. This should be short and simple. This name will be referenced by [build plans](https://concourse.ci/build-plans.html) of jobs in the pipeline.
+*Required.* The name of the resource. This should be short and simple. This name will be referenced by [build plans](https://concourse-ci.org/build-plans.html) of jobs in the pipeline.

headless-services/concourse-language-server/src/main/resources/desc/TaskConfig/image_resource.md

@@ -19,4 +19,4 @@ The following example configures the task to use the `golang:1.6` Docker image:
 
 You can use any resource that returns a filesystem in the correct format (a `/rootfs` directory and a `metadata.json` file in the top level) but normally this will be the [Docker Image resource](https://github.com/concourse/docker-image-resource). If you'd like to make a resource of your own that supports this please use that as a reference implementation for now.
 
-If you want to use an artifact source within the plan containing an image, you must set the [image](https://concourse.ci/task-step.html#task-image) in the plan step instead.
+If you want to use an artifact source within the plan containing an image, you must set the [image](https://concourse-ci.org/task-step.html#task-image) in the plan step instead.

headless-services/concourse-language-server/src/main/resources/desc/TaskConfig/inputs.md

@@ -1,3 +1,3 @@
 *Required.* The expected set of inputs for the task.
 
-This determines which artifacts will propagate into the task, as the [build plan](https://concourse.ci/build-plans.html) executes. If any specified inputs are not present, the task will end with an error, without running.
+This determines which artifacts will propagate into the task, as the [build plan](https://concourse-ci.org/build-plans.html) executes. If any specified inputs are not present, the task will end with an error, without running.

headless-services/concourse-language-server/src/main/resources/desc/TaskConfig/outputs.md

@@ -1,6 +1,6 @@
 *Optional.* The artifacts produced by the task.
 
-Each output configures a directory to make available to later steps in the [build plan](https://concourse.ci/build-plans.html). The directory will be automatically created before the task runs, and the task should place any artifacts it wants to export in the directory.
+Each output configures a directory to make available to later steps in the [build plan](https://concourse-ci.org/build-plans.html). The directory will be automatically created before the task runs, and the task should place any artifacts it wants to export in the directory.
 
 For example, the following task and script would be used to propagate a built binary to later steps:
 

headless-services/concourse-language-server/src/main/resources/desc/TaskStep/task.md

@@ -1,4 +1,4 @@
-Executes a [Task](https://concourse.ci/concepts.html#tasks), either from a file fetched via the preceding steps, or with inlined configuration.
+Executes a [Task](https://concourse-ci.org/concepts.html#tasks), either from a file fetched via the preceding steps, or with inlined configuration.
 
 	task: string
 

vscode-extensions/vscode-concourse/README.md

@@ -1,7 +1,7 @@
 # Concourse Pipeline and Task Editor for Visual Studio Code
 
 This extension provides validation, content assist and documentation hovers
-for editing [Concourse](https://concourse.ci/) Pipeline and Task configuration files.
+for editing [Concourse](https://concourse-ci.org/) Pipeline and Task configuration files.
 
 ## Usage
 
@@ -63,7 +63,7 @@ to its corresponding definition.
 
 ## Limitations
 
-This Vscode Extension is still a work in progress. At the moment only a select few of the [built-in resource-types](https://concourse.ci/resource-types.html)
+This Vscode Extension is still a work in progress. At the moment only a select few of the [built-in resource-types](https://concourse-ci.org/resource-types.html)
 have been fully defined in the Editor's Schema. 
 
 The resource-types that are already defined in the schema are: