Slack - CICD Automation

 Continuous Integration setup 

Before setting up a CI/CD pipeline, you should first familiarize yourself with the Deno environment if you haven't already. On the CI side of things, we'll be using Deno's built-in tools, which allow developers to leverage tools such as GitHub Actions to add steps for testing, linting, and formatting our code.

You'll also need to accomodate requests from your network to a variety of hosts. Refer to Which hosts are involved in the creation and execution of apps created with the Slack CLI? for more details.

In addition, you'll need to obtain a service token to authorize your CI/CD setup. Refer to CI/CD authorization for more details about obtaining, using, and revoking service tokens.

Once you've done those things, you're ready to get started! Let's walk through an example.

Let's take a look at the Virtual Running Buddies sample app.

First, we'll open the deno.jsonc file located at the root of the project:

// deno.jsonc

{
  "$schema": "https://deno.land/x/deno/cli/schemas/config-file.v1.json",
  "fmt": {
    "files": {
      "include": [
        "README.md", 
        "datastores", 
        "external_auth", 
        "functions", 
        "manifest.ts", 
        "triggers", 
        "types", 
        "views", 
        "workflows"
        ]
    }
  },
  "importMap": "import_map.json",
  "lint": {
    "files": {
      "include": [
        "datastores", 
        "external_auth", 
        "functions", 
        "manifest.ts", 
        "triggers", 
        "types", 
        "views", 
        "workflows"
        ]
    }
  },
  "lock": false,
  "tasks": {
    "test": "deno fmt --check && deno lint && deno test --allow-read --allow-none"
  }
}

This file is your configuration file. It allows you to customize Deno's built-in TypeScript compiler, formatter, and linter.

We'll also point to our import map here (import_map.json), which allows you to manage what versions of modules or the standard library are included with your project:

// import_map.json

{
  "imports": {
    "deno-slack-sdk/": "https://deno.land/x/deno_slack_sdk@2.1.5/",
    "deno-slack-api/": "https://deno.land/x/deno_slack_api@2.1.1/",
    "mock-fetch/": "https://deno.land/x/mock_fetch@0.3.0/"
  }
}

Next, we'll look inside the deno.yml file, which is located in the .github/workflows folder for this sample. Its contents are as follows:

# deno.yml

name: Deno app build and testing

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

jobs:
  deno:
    runs-on: ubuntu-latest
    timeout-minutes: 5

    steps:
      - name: Set up repo
        uses: actions/checkout@v3

      - name: Install Deno
        uses: denoland/setup-deno@v1
        with:
          deno-version: v1.x

      - name: Verify formatting
        run: deno fmt --check

      - name: Run linter
        run: deno lint

      - name: Run tests
        run: deno task test

      - name: Run type check
        run: deno check *.ts && deno check **/*.ts

This is the meat and potatoes of our CI setup. The pipeline is kicked off by a push to or pull request from the main branch, and then we run through all the subcommands we want to complete within the jobs/steps section, including setting up our repository and installing Deno.

This also includes calling Deno's task runner to run any unit tests we have created for our custom functions. This allows us to run all of our unit tests automatically, rather than running each one manually from the command line. In this sample, this means all of the files located in the sample app's functions folder ending in test.ts.

If you've created your project by cloning one of our sample apps, note that the .github folder will not be included. You'll need to create it yourself, but you can use the handy dandy Copy button next to the code samples on this page to get started!

While not part of this sample app, you can also generate test coverage reports from your deno.yml file. For more information, refer to Test coverage.

 

Continuous Delivery setup 

On the CD side of things, there are various ways you can deploy Deno projects to the cloud. Your setup will differ based on which platform you choose.

Let's look at an example deploy.yml file, which you would also place in the .github/workflows folder along with your deno.yml file. The steps below need to run within the app folder and are for already-deployed apps only. Its contents are as follows:

# deploy.yml

name: Deploy to Slack Cloud

on:
  push:
    tags: [ '*.*.*' ]

jobs:
  deploy:
    runs-on: macos-latest

    steps:
      - name: Set up repo
        uses: actions/checkout@v3

      - name: Install CLI
        run: curl -fsSL https://downloads.slack-edge.com/slack-cli/install.sh | bash

      - name: Deploy
        run: slack deploy --app ${{ secrets.APP }} --workspace ${{ secrets.WORKSPACE }} --token ${{ secrets.SLACK_SERVICE_TOKEN }}

Central to this file is calling the slack deploy command to deploy your app to Slack's managed infrastructure. Using this command, the latest changes to your app will be deployed to a workspace once pushed/pulled/merged/tagged/etc. as specified in your workflow.