rupakg / jazz

Jazz Serverless Development Platform

Home Page:http://try.tmo-jazz.net/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Jazz Logo Jazz Serverless Platform

Build Status License Gitter Slack Chat

Seamlessly build, deploy & manage cloud-native applications.

Jazz accelerates adoption of serverless services. Jazz comes with a UI that lets developers quickly create serverless services with the click of a button. Its modular design makes it easy to add new integrations.

  • Services - Jazz can help build functions, APIs and static websites. The template-based system makes it easy to define new ones.
  • Deployment Targets - Currently we deploy to AWS (Lambda, API gateway and S3). We plan to support Azure Functions and Docker containers in the near future.
  • Features - Services seamlessly integrate features like monitoring (CloudWatch), logging (ElasticSearch), authentication (Cognito).
  • Deployment & CI/CD - CI/CD platform is driven using Jenkins where it leverages Serverless Framework for deployment of serverless services.
  • SCM - Jazz works with Gitlab as well as Bitbucket.

Jazz is open-sourced and under active development by T-Mobile's Cloud Center of Excellence.

Watch the video preview here.

Install

You can install Jazz in your account using the automated installer.

Try Jazz!

You can try out public preview version of Jazz by registering with your email address here. You will need a registration code which can be requested by joining slack. Once in slack, you can request a registration code.

User Guide

For more details, see the Wiki.

Development

Branching/release flow

  1. Breaking/nontrivial features first go into named feature branches cut from develop
  2. When/if a feature branch is chosen to be included in the next release, it is merged into develop
  3. Release testing happens in develop
  4. When confirmed/vetted, develop is merged into master, and master becomes the current release.
  5. Small fixes explicitly intended for the next release can be PRed directly into develop without first needing a feature branch.

tl;dr master is always the current release, develop is always the current state of the next release. If you want to contribute a PR, recommend you fork and work in a branch off of develop, then PR against develop. Project owners will move you into a feature branch if they deem it necessary.

License

Jazz is released under the Apache 2.0 License

About

Jazz Serverless Development Platform

http://try.tmo-jazz.net/

License:Apache License 2.0


Languages

Language:JavaScript 47.4%Language:TypeScript 19.4%Language:CSS 13.0%Language:HTML 10.4%Language:Groovy 8.8%Language:Python 0.6%Language:Java 0.5%