Difference between revisions of "Continuous Development"

From SatNOGS Wiki
m (typo)
(layout, categories, misc)
Line 1: Line 1:
The Continuous Deployment workflow for both Network and DB consists of the three steps below.
+
== Introduction ==
 +
The Continuous Deployment (CD) workflow for both Network and DB consists of the three steps below.
  
=== GitLab CI ===
+
== GitLab CI ==
  
 
We have two different jobs (stage and production) that are triggered when there is a new merge on dev or master respectively. These jobs can been seen at the [https://gitlab.com/librespacefoundation/satnogs/satnogs-network/blob/dev/.gitlab-ci.yml .gitlab-ci.yml] file on both of these repositories.
 
We have two different jobs (stage and production) that are triggered when there is a new merge on dev or master respectively. These jobs can been seen at the [https://gitlab.com/librespacefoundation/satnogs/satnogs-network/blob/dev/.gitlab-ci.yml .gitlab-ci.yml] file on both of these repositories.
  
=== GitLab Variables ===
+
== GitLab Variables ==
  
 
GitLab hosts some secret variables for each environment. Such as IP address, ssh keypairs, etc. GitLab CI uses that variables to remotely push the new code to the servers.
 
GitLab hosts some secret variables for each environment. Such as IP address, ssh keypairs, etc. GitLab CI uses that variables to remotely push the new code to the servers.
  
=== Git Hooks ===
+
== Git Hooks ==
  
 
On servers there is a post-update git hook that runs the deployment tasks (collectstatic, reload gunicorn, etc), on each push.
 
On servers there is a post-update git hook that runs the deployment tasks (collectstatic, reload gunicorn, etc), on each push.
 +
 +
== See also ==
 +
* [https://gitlab.com/librespacefoundation/ Libre Space Foundation GitLab]
 +
 +
[[Category:Development]]
 +
[[Category:Infrastructure]]

Revision as of 21:15, 19 January 2020

Introduction

The Continuous Deployment (CD) workflow for both Network and DB consists of the three steps below.

GitLab CI

We have two different jobs (stage and production) that are triggered when there is a new merge on dev or master respectively. These jobs can been seen at the .gitlab-ci.yml file on both of these repositories.

GitLab Variables

GitLab hosts some secret variables for each environment. Such as IP address, ssh keypairs, etc. GitLab CI uses that variables to remotely push the new code to the servers.

Git Hooks

On servers there is a post-update git hook that runs the deployment tasks (collectstatic, reload gunicorn, etc), on each push.

See also