Skip to content

Project plan

Siarhei Pishchyk edited this page Dec 29, 2019 · 2 revisions

Common

Project demo should contain:

  • scheme of flow/pipelines
  • repository of your code (pipeline)
  • working pipeline
  • demo shouldn't be not longer than 10 mins

Application requirements:

  • Versioning
  • DB inside
  • User data

As example can be any from this list of CMS

CI

Organize CI:

  • Git repository for application
    • branches, README.md
  • Git repository for pipeline code
    • branches, README.md
  • Push/merge/commit reaction
    • Code validation
    • Container deployment/image build
    • Any kind of tests

CD

Develop and delivery CD solution for your application:

Pipelines:

  • Green deployment
  • Upgrade (keep user data)
  • Rollback if deployment failed
  • Notification
  • Performance testing for your Pipeline

Example of project report

Project's reporter: First Name, Surname

Group number: m-sa2-XX-XX

Description of application for deployment

  • Name of application
  • Which programming language is this application written in
  • What kind of DB
  • Link on git repository/site/package repository

Pipeline. High Level Design

Scheme here

Technologies which were used in project

Orchestration: Jenkins, git runners, cron, kubeplayer ...

Automation tools: Ansible, puppet, bash, python....

CI description: by hook/schedule/poll, tests, checks ....

Deployment flows short description:

How does new/upgrade deployment work

Rollback flow description and implementation:

How does rollback work, triggers ...

Links

The link your repository of Pipeline code Another links Another links