1 files changed, 53 insertions, 0 deletions
diff --git a/lua/lspconfig/server_configurations/azure_pipelines_ls.lua b/lua/lspconfig/server_configurations/azure_pipelines_ls.lua
new file mode 100644
index 00000000..38d2c6a4
--- /dev/null
+++ b/lua/lspconfig/server_configurations/azure_pipelines_ls.lua
@@ -0,0 +1,53 @@
+local util = require 'lspconfig.util'
+
+return {
+  default_config = {
+    cmd = {},
+    filetypes = { 'yaml' },
+    root_dir = util.root_pattern 'azure-pipelines.yml',
+    single_file_support = true,
+    settings = {},
+  },
+  docs = {
+    description = [[
+https://github.com/microsoft/azure-pipelines-language-server
+
+An Azure Pipelines language server
+
+**By default, `azure-pipelines-ls` doesn't have a `cmd` set.** This is because nvim-lspconfig does not make assumptions about your path.
+You have to install the language server manually.
+
+`azure-pipelines-ls` can be installed via `npm`:
+
+```sh
+npm install -g azure-pipelines-language-server
+```
+
+Once installed, point `cmd` to `server.js` inside the `out` directory:
+
+```lua
+cmd = {'node', '<path_to_azure_pipelines_install>/out/server.js', '--stdio'}
+```
+
+By default `azure-pipelines-ls` will only work in files named `azure-pipelines.yml`, this can be changed by providing additional settings like so:
+```lua
+require("lspconfig").azure_pipelines_ls.setup {
+  ... -- other configuration for setup {}
+  settings = {
+      yaml = {
+          schemas = {
+              ["https://raw.githubusercontent.com/microsoft/azure-pipelines-vscode/master/service-schema.json"] = {
+                  "/azure-pipeline*.y*l",
+                  "/*.azure*",
+                  "Azure-Pipelines/**/*.y*l",
+                  "Pipelines/*.y*l",
+              },
+          },
+      },
+  },
+}
+```
+The Azure Pipelines LSP is a fork of `yaml-language-server` and as such the same settings can be passed to it as `yaml-language-server`.
+]],
+  },
+}