You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

 

How to deploy files to service.un.org

Table of Contants

This how-to describes process of getting files from your local PC to service.unece.org using Repositories and Pipelines. Should be reffered to typically when a new version of UN/EDIFACT, UN/LOCODE or other deliverable hosted on service.unece.org is produced and needs to be published.

Terms

Local Repository - Folders and files on your Local PC,

Remote Repository - Folders and files on remote Server, these files are used by Pipeline

Clone - Process of copying files from the Remote Repository to the Local Repository

Commit - Finalazing a change in files, should contain commed describing reason of the change

Push - Process of moving changes from Local Repository to Remote Repository, One Push can contain multiple commits

Pipeline - Automated process for moving files between environments (typicaly Remote Repository → Stage → Production)

Stage - Staging / Testing / Quality Assurance (QA) environemnt, serves for final validation of files before moving them into Production environemtn (service-qa.unece.org)

Production - Production environment, final destination of our files (service.unece.org)

(not covered, Pull, Pull-request, Branch, Merge, another billion of Git's features etc. ...)

Diagram

Simplified diagram of the whole process:

Files-Deployment

Resources

Repository Web interface

Repository GUI

Pipeline Web interface

Installing tools

Working with Git

Official Sourcetree documentation

Step-by-step guide

Cloning Repo

Adding changes

Commiting to Repo

Running Pipelines

From repo to Stage

From Stage to Prod

86 this section

Prerequisities

 

Step-by-step guide

 

  • No labels

This page has no comments.