Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

As a keptn developer, I can automatically set up a demo environment #206

Closed
dirkwall opened this issue Mar 27, 2019 · 3 comments
Closed
Assignees
Labels
type:chore Provides value to the (dev) team

Comments

@dirkwall
Copy link
Contributor

dirkwall commented Mar 27, 2019

We have an on-demand dedicated demo environment, where that latest features and overall use cases can be demonstrated. This environment can also be used for sprint reviews and community meetings.

Acceptance criteria

  • Given I'm a person that gives a demo
    When I get a fresh Kubernetes cluster
    Then I want to be able to install keptn including all core components automatically
@dirkwall dirkwall added type:chore Provides value to the (dev) team area:infra labels Mar 27, 2019
@dirkwall dirkwall added this to the backlog milestone Mar 27, 2019
@dirkwall dirkwall changed the title As a keptn developer, I have a demo environment that is updated on a regular basis As a keptn developer, I have a demo environment that can be set up in an automated fashion Mar 28, 2019
@dirkwall dirkwall changed the title As a keptn developer, I have a demo environment that can be set up in an automated fashion As a keptn developer, I can automatically set up a demo environment Mar 28, 2019
@dirkwall dirkwall added the 5 label Mar 28, 2019
@agrimmer agrimmer self-assigned this Apr 8, 2019
@agrimmer agrimmer removed their assignment Apr 8, 2019
@agrimmer agrimmer assigned agrimmer and unassigned agrimmer Apr 8, 2019
@agrimmer agrimmer self-assigned this May 2, 2019
@agrimmer
Copy link
Member

agrimmer commented May 2, 2019

During the night, a travis cron job sets up a new environment and installs keptn in the version of the dev-branch.

Refinement of Then: keptn is automatically installed by the travis cron job

@agrimmer
Copy link
Member

agrimmer commented May 7, 2019

Completed:

  • Setup of a nightly-cluster using keptn in version 0.2.1. This cluster is re-created on a daily basis using a Travis cron job.
  • End-to-end tests verify the functionality

Missing due to dependencies on issue #327:

  • The nightly cluster should be set up using the versions contained in the dev-branches of the core components.
  • Extend end-to-end tests: (1) test which pushes an artifact into dev, staging and prod, (2) test with quality gates in place
  • Rename scripts: Currently, the scripts are named 'pr_main' and 'master_main'. These names are misleading.

agrimmer added a commit that referenced this issue May 7, 2019
@dirkwall
Copy link
Contributor Author

dirkwall commented May 8, 2019

Closing this issue. Missing tasks are transferred to #337

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type:chore Provides value to the (dev) team
Projects
None yet
Development

No branches or pull requests

2 participants