gitploy-io · noahingh · Feb 27, 2022 · Feb 27, 2022 · Feb 27, 2022
diff --git a/docs/concepts/self-hosted-server.md b/docs/concepts/self-hosted-server.md
diff --git a/docs/tasks/integration.md b/docs/tasks/integration.md
@@ -4,51 +4,164 @@ sidebar_position: 3
 
 # Integration
 
-## GitHub Action
+## Deployment API
 
-GitHub Actions help you automate tasks to run an actual deployment. GitHub Actions are event-driven, meaning that you can run a series of commands after a deployment event has occurred. 
+As described in the '[How it works](../concepts/how-it-work.md)' document, two preparations are required to connect with the deployment API; 1) Make sure your deployment tooling is listening for the Github [deployment](https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment) event. 2) Update the deployment status by [API](https://docs.github.com/en/rest/reference/deployments#create-a-deployment-status) after execution is complete. This document will show how you can connect with the mainstream deployment tools.
 
-To listening the deployment event, you must specify `deployment` for the `on` field. And you can use the `if` conditional to run a job for the specific environment. Here is the example below.
+### GitHub Action
+
+#### Listening for an event
+
+GitHub Action provides the `on` syntax to define the type of activity that will trigger a workflow run, and it supports the deployment event. 
 
 ```yaml
-# Listening the deployment event
 on:
   deployment
+```
 
+And you can use the `if` conditional to run a job when an environment is met. You can use context to access the deployment environment.
+
+```yaml
+jobs:
+  deploy-production:
+    runs-on: ubuntu-latest
+    if: ${{ github.event.deployment.environment === 'production' }}
+```
+
+#### Update the deployment status
+
+The third-party plugin, [chrnorm/deployment-status](https://github.com/chrnorm/deployment-status), provides that a GitHub action updates the status of deployments as part of your GitHub CI workflows.
+
+
+```yaml
 jobs:
   deploy-dev:
     runs-on: ubuntu-latest
-    # Run a job when the environment is 'production.
-    if: ${{ github.event.deployment.environment == 'production' }}
     steps:
-      -
-        name: Checkout
-        uses: actions/checkout@v2
+      ...
       - 
-        name: Start to deploy
+        name: Update the deployment status
         uses: chrnorm/deployment-status@releases/v1
         with:
-          deployment_id: ${{ github.event.deployment.id }}
-          description: Start to deploy ...
-          state: "in_progress"
           token: "${{ github.token }}"
-    # Run your deployment commands.
+          deployment_id: ${{ github.event.deployment.id }}
+          description: Finish to deploy successfully.
+          state: "success"
 ```
 
-## Slack
+You can reference this [example](https://github.com/gitploy-io/gitploy/discussions/178) for integrating with GitHub action.
+
+### Drone CI
+
+#### Listening for an event
+
+Drone CI provides the `trigger` field to limit pipeline execution based on the drone event type, supporting the `promote` event. 
+
+```yaml
+trigger:
+  event:
+  - promote
+```
+
+And you can access the [`DRONE_DEPLOY_TO`](https://docs.drone.io/pipeline/environment/reference/drone-deploy-to/) environment by the environment if you need the conditional step. 
+
+#### Update the deployment status
+
+The third-party plugin, [cedrichopf/drone-status](https://github.com/cedrichopf/drone-status), provides that a Drone CI updates the status of deployments as part of your CI pipelines.
+
+```yaml
+steps:
+  - name: Update the deployment status
+    image: cedrichopf/drone-status
+    settings:
+      api_token:
+        from_secret: GITHUB_TOKEN 
+      context: deploy
+      state: success
+      description: Finish to deploy successfully.
+```
+
+### Spinnaker
+
+#### Listening for an event
+
+The trigger type has to be the webhook type to listen to an event, and the constraints verify repository and environment to determine if triggered or not. 
+
+![Spinnaker Webhook Trigger](../../static/img/docs/spinnaker-trigger.png)
+
+#### Update the deployment status
+
+Spinnaker provides a simple way to add a custom stage to call API instead of extending through codes. Spinnaker can typically make API calls as part of a pipeline by adding a custom stage.
+
+To create a custom webhook, we have to add the configuration to the `orca-local.yml` file, located in `$HOME/.hal/default/profiles`. And the custom stage has a few variables, `owner`, `repo`, `deployment_id`, `description`, and `state`, for updating the deployment status dynamically. You can set up the variables for your project.
+
+<details>
+<summary>Custom Stage</summary>
+
+```yaml
+webhook:
+  preconfigured:
+    - label: Update Deployment status
+      type: updateDeploymentStatus
+      enabled: true
+      description: Update the deployment status.
+      method: POST
+      url: https://api.github.com/repos/${ parameterValues['owner'] }/${ parameterValues['repo'] }/deployments/${ parameterValues['deployment_id'] }/statuses
+      customHeaders:
+        # Replace with your GitHub token.
+        Authorization:
+          - token GITHUB_TOKEN
+        Content-Type:
+          - application/json
+      payload: |-
+        {
+          "description": "${parameterValues['description']}",
+          "state": "${parameterValues['state']}",
+          "log_url": "http://localhost:9000/#/applications/${execution.application}/executions/details/${execution.id}"
+        }
+      parameters:
+        - label: GitHub Owner
+          name: owner
+          type: string
+        - label: GitHub Repo
+          name: repo
+          type: string
+        - lable: Deployment ID
+          name: deployment_id
+          type: string
+        - label: Description
+          name: description
+          type: string
+        - label: State
+          name: state
+          type: string
+          description: The state can be one of "queued", "in_progress", "success", "failure"
+```
+
+</details>
+
+You can reference the [spinnaker demo](https://github.com/gitploy-io/spinnaker-demo) for integrating with Spinnaker.
+
+
+
+### Internal Deployment Tooling
+
+GitHub provides a well-organized [document](https://docs.github.com/en/rest/guides/delivering-deployments) to guide to build an internal deployment tooling to deploy on your servers with the Deployment API. 
+
+## Notification
 
-Slack integration provides notifications for events.
+### Slack
 
-### Step 1: Create App
+#### Step 1: Create App
 
 Firstly, we have to create [Slack App](https://api.slack.com/apps). You should click the Create App button and fill out inputs.
 
-### Step 2: Configure Permissions
+#### Step 2: Configure Permissions
 
 After creating App, we move to the *OAuth & Permissions* page and set up *the redirect URLs* and *Bot Token scopes*on this page. Firstly, you should add a new redirect URL with the `GITPLOY_SERVER_PROTO://GITPLOY_SERVER_HOST/slack/signin` format; secondly, add `chat:write` scope into the Bot Token scopes.
 
 ![Slack Bot Token Sceops](../../static/img/docs/slack-bot-token-scopes.png)
 
-### Step 3: Run Server With App Credentials
+#### Step 3: Run Server With App Credentials
 
 To enable Slack integration, you have to set up these environments when you run the server: `GITPLOY_SLACK_CLIENT_ID` and `GITPLOY_SLACK_CLIENT_SECRET`. You can get these credentials from *App Credentials* section of *Basic Information* page. 
diff --git a/static/img/docs/spinnaker-trigger.png b/static/img/docs/spinnaker-trigger.png