Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 277
    • Issues 277
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #32
Closed
Open
Issue created 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
Time tracking