Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
stork
stork
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 138
    • Issues 138
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • storkstork
  • Issues
  • #32

Closed
Open
Opened Oct 14, 2019 by Tomek Mrugalski@tomek🛰Owner

CD (Continuous Delivery) - develop automated deployment to stork.lab.isc.org

During exec discussions about Stork, there was a request from Sales team to have something useful for a kind of demo system. We're still several months away from having anything useful enough to be users worthy, but we should start thinking about our processes to deploy master (or perhaps selected builds) to stork.lab.isc.org.

The goal of this issue to came up with:

  1. some rules proposal when to deploy updated code (every commit to master, every commit that passed jenkins tests, perhaps only manually?)
  2. develop scripts that will make the deployment possible.
Assignee
Assign to
Stork-0.3
Milestone
Stork-0.3 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/stork#32