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

Compare with Current View Page History

« Previous Version 14 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

Working with Git

Official Sourcetree documentation

Step-by-step guide

Installing and Configuring tools

Sourcetree Initial configuration 

  • Download and install Sourcetree, if needed install also MS .NET Framework 7.4.1, as this requires Administrator privilegies, ask ISU for assistance
  • After Installation run Sourcetree application
  • As part of initial execution, configure Sourcetree - useraccount and tools

    1. Login to remote Repository 
    2. Authenticate user (using Windows / Active Directory credentials)
    3. If Credentials are correct, you should see confirmation
    4. Select modules for installation (we need only Git)
    5. Module installation - progress
    6. Module installation - confirmation
    7. SSH key configuration (can be skipped)


  • After Initial setup we configure and clone repositories
    1. Add a new repository
    2. On remote server, click "Clone in SourceTree" for easy configuration, or copy repository link (for Git repositories the link ends with .git)
    3. Review Cloning configuration, select local folder where files shoud be stored
    4. Run Clone and wait for process to finish

Cloning Repository

Commiting and Pushing changes to Repository

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.