Lifecycle of your Jazz service - dev9com/jazz GitHub Wiki

This page details the lifecycle of your Jazz services from creation stage to deployment to different environments.

Overview

  1. Create your service using Jazz self-service portal. Your service details page will have a link to the repository that comes preloaded with the appropriate service template.
  2. You are now ready to make changes to your code. Some of the files in your template and their purposes -
    • handler file has the core application logic
    • deployment-env.yml file has the service & deployment related configurations
    • swagger.json has the API specifications (for service type API)
  3. Once you are ready with your code changes, commit to a feature or a bugfix branch to trigger deployment. Remember that code changes made to master branch directly will be rejected
  4. This triggers a Jenkins workflow that does the CI/CD for your service in development environment.
  5. On a successful deployment, service owner gets an email with the service endpoint details. For example, for function in AWS, you will receive the function's ARN (Amazon Resource Name).
  6. When the service owner wants to move their branch code to master, they would raise a pull request. Merge event to the master branch will trigger similar CI/CD workflow that deploys your service to production environment.