circleci

README.md

Separate Serverless build and deploy.

Steps

• Build: run serverless package, and cache the packaged content
• Deploy: load the cached package, run serverless deploy with the --package option and save time on packaging.

Why?

1. Easier to troubleshoot
2. There's a known issue with serverless-plugin-typescript building too slowly. The more functions per stack, the slower the build is. If deployment fails because of some IAM permission issues, we can re-run from failed and save some time on the build. The built artifacts are already cached using save_cache, we just need to load them
3. In the future we can integrate with an artifactory (e.g. JFrog etc)

config.yaml

jobs:
  build:
    steps:
      - run:
          command: |
            npx serverless package --region us-east-1 --stage $CIRCLE_BRANCH
            cp ./.serverless ./artifacts -r
      - save_cache:
          key: envs-{{ .Revision }}
          paths:
            - ~/project/node_modules
            - ~/project/artifacts
            - ~/.envs

  deploy:
    steps:
      - restore_cache:
          key: envs-{{ .Revision }}
      - run:
	  command: npx serverless deploy --region us-east-1 --stage $CIRCLE_BRANCH --package ./artifacts