UN/CEFACT Collaboration Environment

Space shortcuts

Page tree

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

Compare with Current View Page History

« Previous Version 16 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)

Cloning Repository

  • 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 click on "Clone" and 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

Making a change

  • Local repo without a change (local repo in sync with the remote repo)

  • Local repo in windows explorer
  • New files (selected) to be transferred to local repo in windows explorer
  • Transfer to local repo running
  • We have a new files (we updated the current files) in our local repo (this is considedred as a change, another type of change is adding and removing files/folders) 
    1. New files in local repo - file status
    2. New files in local repo - Commit Log
    3. Diff - one line change example
    4. Diff - new lines example
    5. Diff - Line change example (- removed, + added)
    6. Files Staged
    7. Adding commit message
    8. Commit user info
    9. Adding mail
    10. Commit is linked to user account
    11. After commit - back in sync a Push is available
    12. After commit - Log - Push prepared
    13. Push branch selection
    14. Push running
    15. Push completed
    16. Bitbucket - Remote repo - Commits
    17. Bitbucket - Remote repo - Sources

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.

© United Nations Economic Commission for Europe | Trade Division | UN/CEFACT

 

UNECE Staff members are authorized to login with their network credentials (i.e. login/pwd to access their Desktop computer)


Access to this system is restricted to members of UN/CEFACT Community only : UNECE Staff, UN/CEFACT Bureau, Heads of Delegations, Domain Coordinators and UN/CEFACT Experts. All information contained in or obtained from this system is to be used exclusively for UN/CEFACT official purposes. In proceeding, the user agrees to comply with all UN/CEFACT Policies, Procedures and Terms of Reference and with the UN/CEFACT Code of Conduct.