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 not covered: Pull (to be added), Pull-request, Branch, Merge, other Git's features) |
Simplified diagram of the whole process:
Repository Web interface
Repository GUI
Pipeline Web interface
Official Sourcetree documentation
As part of initial execution, configure Sourcetree - useraccount and tools
Before you perform any changes in your local files, be sure you have the latest state of remote repository synchronized with your local repository to do this we perform "Pull" action, this will retrieve the latest files from remote repository and update the local one, this will also make sure we are working on the latest version of files and generally prevent conflicts when commiting changes. and confirm pull from master branch |
Local repo without a change, after Initial Cloning we have a files in Local Repo the same state as they appear on Remote Repo (local repo is in sync with the remote repo)
Transfer to local repo Overwrite prompt (if updating files to a new version)
Select desired Pipeline (in our case, as we are deploying new LOCODE Directory version - we use "Service LOCODE" pipeline)
Deploy to Stage - running
Deploy to Stage - completed
Changes appear on Stage for validation (service-qa.unece.org)