Skip to content
keptn is a control-plane for continuous delivery and operations enable cloud-native applications to run autonomously
Branch: master
Clone or download
Latest commit be19a22 Apr 25, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Update bug_report.md Feb 21, 2019
assets not needed anymore Feb 14, 2019
cli Print message to which server the command is sent Apr 10, 2019
core fixed unit tests Apr 18, 2019
designDocs Merge branch 'master' into delete-obsolete-files Mar 18, 2019
install Fixed wrong if clause Apr 17, 2019
releasenotes Create releasenotes_V0.2.1.md Apr 24, 2019
test Changed file permission for script. Feb 19, 2019
travis-scripts fixed test script Apr 16, 2019
.gitignore updated gitignore Apr 5, 2019
.travis.yml
CODEOWNERS Update CODEOWNERS Apr 25, 2019
CODE_OF_CONDUCT.md Update CODE_OF_CONDUCT.md Feb 21, 2019
LICENSE Update LICENSE Feb 7, 2019
README.md fix link Apr 10, 2019

README.md

Build Status

keptn

keptn

keptn is a fabric for cloud-native lifecycle automation at enterprise scale. In its first version it provides an automated setup of the keptn core components as well as a demo application. Also included are three preconfigured use cases for the demo application: automated quality gates, runbook automation, and automated evaluation of blue/green deployments.

Usage

Here is the best way to getting started with keptn:

  • If you want to try out the latest stable release with your own services and application, please head over to the release section of keptn and follow the official documentation of keptn.
  • If you want to try out the latest version of keptn with your own services and application, please use the 0.2.x release branch and follow the documentation on the https://keptn.sh website. We recommend to work with this version.
  • If you want to work with the latest version of keptn that is currently under development, please use the master branch. (⚠️ this is the development branch, so it might not be stable all the time)
  • Please use the docs on the keptn website to get resources on how to use keptn.
  • Please use the release section to learn about our current releases, release candidates and pre-releases to get the latest version of keptn.

Repositories

  • keptn/keptn. This is the main repository that you are currently looking at. It hosts keptn's core components and documents that govern the keptn open source project. It includes:
    • designDocs: We're already designing the architecture and use cases for the next releases - you can find the current design docs here. Please feel free to review and comment the designs, after all, we're encouraging all of you to collaborate on keptn.
    • install: This directory contains all artifacts that are required to install keptn. Please note that the latest docs can be found in the docs section of the keptn website.
    • releasenotes: You can find the current release notes in this directory.

Versions compatibilities

We mangage the keptn core components as well as all services (e.g. Jenkins-service, GitHub-service) in versions. The respective images in their versions are stored in DockerHub. The versions of the keptn core components and the services have to be compatible to each other. Therefore, this section shows the compatibility between these versions.

keptn in version 0.2.0 requires:

  • keptn/keptn-authenticator:0.2.0
  • keptn/keptn-control:0.2.0
  • keptn/keptn-event-broker:0.2.0
  • keptn/keptn-event-broker-ext:0.2.0
  • keptn/pitometer-service:0.1.0
  • keptn/servicenow-service:0.1.0
  • keptn/github-service:0.1.0
  • keptn/jenkins-service:0.1.0
    • keptn/jenkins:0.4.0

keptn in version 0.1.3 requires:

  • keptn/jenkins:0.2
  • dynatraceacm/ansibletower:3.3.1-1-2

Further information

  • The keptn website has the documentation of keptn and its usecases.
You can’t perform that action at this time.