DOCSLIB.ORG

Version Control System Version 7.18 This Documentation Is Provided Under Restrictions on Use and Are Protected by Intellectual Property Laws

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Version Control System Version 7.18 This Documentation Is Provided Under Restrictions on Use and Are Protected by Intellectual Property Laws Version control system Version 7.18 This documentation is provided under restrictions on use and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this documentation, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. © 2021 Creatio. All rights reserved. Table of Contents | 3 Table of Contents Version control in Creatio IDE 5 Committing a package to storage 5 Installing packages from repository 6 Updating package from repository 6 Committing a package to repository 6 Installing packages from repository 7 Package installation sequence 7 Changes in package hierarchy 9 Updating package from repository 10 The sequence of package update from SVN 11 Version control in Subversion 11 General outline 12 Versioning models 13 Determining the state of the working copy file 13 Working copy used in Creatio 14 Using an application to work in SVN 14 Create a package in the file system development mode 14 1. Create a package in the application 15 2. Download created package to file system 16 3. Create necessary folders for the packages in the SVN repository 17 4. Create a working copy of the package version branch 18 5. Commit the package folder in the repository 20 Install an SVN package in the file system development mode 21 The procedure for installing an SVN package in the file system development mode 21 Case description 22 Case implementation algorithm 22 Bind an existing package to SVN 26 The general sequence for binding a package to the repository 26 Case description 26 Case implementation algorithm 27 Alternative implementation 33 Update and commit changes to the SVN from the file system 35 Case description 35 Updating the package 35 Package contents modifications 37 Committing a package to storage 38 © 2021 Creatio. All rights reserved. Table of Contents | 4 Create the package and switch to the file system development mode 39 Introduction 39 Case description 39 Case implementation algorithm 39 Version control in Git 45 Introduction 46 Working with Git in Creatio 46 Configure working with Git 46 Step 1. Enable the file system development mode 46 Step 2. Create a package without binding it to the repository 46 Step 3. Create the required package schemas. 47 Step 4. Export the package to the file system. 47 Step 5. Add the required source code 48 Step 6. Commit the changes to the version control system 48 Step 7. Install an updated package in the application 49 Step 8. Generate source codes 50 Step 9. Compiling the changes 50 Step 10. Updating the database structure 50 Step 11. Installing SQL scripts and bound data 50 © 2021 Creatio. All rights reserved. Version control in Creatio IDE | 5 Version control in Creatio IDE Easy Creatio IDE implements a set of tools for working with the SVN version control system. Commiting a package, updating a package or installing it from a repository using the built-in Creatio tools is not possible when development mode is enabled in the file system. Committing a package to storage Committing package to storage is adding all package modifications to the SVN storage. Packages are commited manually. Modifications of other configuration packages are not committed. Package committing is required when: creating a new package adding new and modifying existing package components deleting package components modifying package properties The system displays the names of custom packages that have not been committed yet and the name of the storage the packages will be committed to (1). The SVN revision number is not displayed. and will be added after the committing. Such packages are locked by default. The system displays the names of custom packages that have already been committed, the name of the storage and the latest SVN revision number. The basic package is displayed in the same way as the custom package (2). If a custom package has been modified, its name will be displayed in bold (3). Attention. If an element was deleted from a package (for example, schema or SQL script), then those modifications won’t affect the package display. © 2021 Creatio. All rights reserved. Committing a package to repository | 6 Installing packages from repository Installing a package from the repository is adding the package and all its dependencies from the version control system repository (SVN) to Creatio. Package installation is required when: Multiple developers work on the package functionality. Changes are transferred between applications. Updating package from repository The package upgrade process is downloading to the application all changes of the selected package and all its dependencies changes from the version control system storage (SVN). Committing a package to repository Easy To commit a package to storage, first, select it on the [ Packages ] tab. In the context menu, select the [ Commit package to storage ] action. Attention. When the file system development mode is enabled, the SVN integration mechanism is turned off. Therefore, the [ Commit package to repository ] action is unavailable. As a result, the [ Changes ] window will open. © 2021 Creatio. All rights reserved. Installing packages from repository | 7 You must add a comment in the [ Description ] window when committing a package. For example, describe the modifications made to the package. The committed files are displayed in the bottom of the window. After pressing the [ Commit Changes to Repository ] button, the package will be committed and the modifications will be become available for other system users. Attention. The is committed to the storage specified in its properties. Packages can only be committed to an active storage. When a package is committed, the lock is removed. The package and its components become available for other system users. Installing packages from repository Easy Attention. The information below are applicable when working with SVN repositories via the Creatio built-in development tools. The information are not applicable when the file system design mode is turned on (see "Version control in Subversion"). Package installation sequence Attention. Before updating the application via SVN, you must back up the database. If the application is deployed in the cloud, you should contact support. Please note that you cannot revert to the previous version of the application via SVN. The package is installed from the repository using the actions in the [ Configuration ] section. More details about this section tools can be found in the "The [ Configuration ] section” article. To install the package from the repository, go to the [ Configuration ] section, right-click the [ Packages ] tab and © 2021 Creatio. All rights reserved. Installing packages from repository | 8 select the [ Install Package from Repository ] option. Then, in the dialog box, select the repository, the name and version of the package to install, and then click the [ Install ] button. During the package installation, the bound data will be automatically applied, and dependencies will be installed. If, for any reason, the automatic application of changes has not been enabled, then changes must be applied manually. To do this, perform the following actions for the installed package in the [ Configuration ] section: 1. Generate the source codes for items that require it. 2. Compile the modified items. 3. Update the database structure. 4. Install SQL scripts if necessary. 5. Install the connected data. Note. Checkboxes in the [ Database Update Required ] and [ Require database installation ] columns on the [ Schemas ], [ SQL scripts ] and [ Data ] tabs of the [ Configuration section ] indicate that a schema, script or data needs to be installed in the database or requires modification of the database structure. In case of errors, the text of the last error can be seen in the [ Last error message text ] column. Please note that not all of these columns are displayed on the [ Schemas ], [ SQL scripts ] and [ Data ] tabs of the [ Configuration ] section. If necessary, you can add them using the [ Columns setup ] context menu. Attention. After installing or updating a package from SVN, Creatio application requires compilation (the [ Compile all items ] action in the [ Configuration ] section). In the process of compilation, the static content © 2021 Creatio. All rights reserved. Installing packages from repository | 9 will be generated (see "Client static content in the file system" article). Changes in package hierarchy When you install a custom package, the system checks its dependencies and optionally installs or upgrades all the packages the current package depends on. For example, when you install the [ UsrCustomPackage ] package from the repository, the [ UsrDependentPackage ] package dependency will also be installed. This modifies the package hierarchy in the application. When a custom package is installed from SVN, the package hierarchy will be modified in the following way: 1) The application detects all dependencies of the installed package specified in its metadata in the DependsOn © 2021 Creatio. All rights reserved. Updating package from repository | 10 property. { "Descriptor": { "UId": "8bc92579-92ee-4ff2-8d44-1ca61542aa1b",
Load more

Recommended publications
  • Tortoisemerge a Diff/Merge Tool for Windows Version 1.11
    TortoiseMerge A diff/merge tool for Windows Version 1.11 Stefan Küng Lübbe Onken Simon Large TortoiseMerge: A diff/merge tool for Windows: Version 1.11 by Stefan Küng, Lübbe Onken, and Simon Large Publication date 2018/09/22 18:28:22 (r28377) Table of Contents Preface ........................................................................................................................................ vi 1. TortoiseMerge is free! ....................................................................................................... vi 2. Acknowledgments ............................................................................................................. vi 1. Introduction .............................................................................................................................. 1 1.1. Overview ....................................................................................................................... 1 1.2. TortoiseMerge's History .................................................................................................... 1 2. Basic Concepts .......................................................................................................................... 3 2.1. Viewing and Merging Differences ...................................................................................... 3 2.2. Editing Conflicts ............................................................................................................. 3 2.3. Applying Patches ...........................................................................................................
    [Show full text]
  • Introduction to Subversion
    Introduction to Subversion Wendy Smoak Rob Richardson Desert Code Camp, October 2006 Wendy Smoak ● Sr. Systems Analyst, Arizona State University – Web application development – Systems and database administration ● Member, The Apache Software Foundation – Struts, MyFaces, Shale, Maven – Infrastructure, release management, documentation ● Contact me: – [email protected] – http://www.wsmoak.net Rob Richardson ● Principal, Richardson & Sons – Provides enterprise software development for small- to medium-sized businesses. – Has created software applications raging from enterprise-scale applications to PDA-based systems, web applications to embedded database synchronization and postscript processing systems. – Specializes in translating business requirements into technical solutions. – Our business is listening to your needs and building you effective tools. ● My Qualifications – Masters of Science in Computer Information Systems (MSCIS) – Bachelors of Fine Arts in Industrial Design (BFA ID), the study of human factors and human / technology interaction – Over 10 years of software development experience ● Contact me: – richardsonandsons.com/contact.aspx What is source control? ● A central place to store your code – Backup and recovery ● Records a history of code changes ● Facilitates collaboration among development team members ● Easy to check out prior code, undo changes, version products How does source control work? User1 Import Create Project or Add Update The Repository User2 Working Copy Commit Check Out User3 Working Copy Why should I use source control? ● Because the alternative is frightening beyond all reason ● Some motivation: “Well, I'd been working on the code, and got it to a state where I was prepared to share it. Then I thought I'd clean up the target directory and do a new build just to be sure.
    [Show full text]
  • Getting Started with Subversion (Migrating from CVS to SVN) Version 1.0 Frank C
    Getting Started with SubVersion (Migrating from CVS to SVN) Version 1.0 Frank C. Anderson Department of Mechanical Engineering, Stanford University [email protected] SimTK.org uses SVN (SubVersion, http://subversion.tigris.org) as its source-code versioning system. It stores a revision history for files under version control in a repository and enables potentially large numbers of programmers to work on source code concurrently. It is intended to replace CVS (Concurrent Versions System, http://www.cvshome.org). Some of the key improvements over CVS include: • Repository-wide version numbering. Each time a change is committed to the SVN repository, the revision number of the entire repository is incremented. This is in contrast to CVS, which keeps revisions on a per-file basis. The versioning system used by SVN allows for easier retrieval of self-consistent snapshots of the code. • Directories and renames are versioned. This allows one to change the names of files and directories and reorganize a repository, something that is difficult to do in CVS. • Efficient versioning of binary files. All diffs in SVN are on a binary basis, thus text files and binary files are handled the same. • Branching and Tagging are inexpensive. Branching is the mechanism for making major code revisions without breaking the main development trunk. Tagging is the mechanism for making release snapshots. Both mechanisms use the copy command. In SVN, copies are done through symbolic links, so the disk space that is needed only for changes that are made in the files. Using SVN is much like using CVS; many of the commands are the same.
    [Show full text]
  • Tutorial 0: SVN ECSE 321 – Intro to Software Engineering Electrical and Computer Engineering Mcgill University Winter 2009
    Tutorial 0: SVN ECSE 321 – Intro to Software Engineering Electrical and Computer Engineering McGill University Winter 2009 1. Introduction………………………………………………………………………..1 2. Step 1: Desktop Setup……………………………………………………………..1 3. Step 2: Registering………………………………………………………………...1 4. Step 3: Creating a Project Space…………………………………………………..1 5. Step 4: Accessing your Project Space…………………………………………….4 6. Step 5: Installing Subversion (SVN) ……………………………………………........4 7. Step 6: Installing TortoiseSVN……………………………………………………4 8. Step 7: Checking out your Folder…………………………………………………5 9. Step 8: Completing your Checkout………………………………………………..5 10. SVN Commands…………………………………………………………………..6 Introduction In the field of software development, the Concurrent Versions System (CVS), also known as the Concurrent Versioning System, is a free software revision control system. Version control system software keeps track of all work and all changes in a set of files, and allows several developers (potentially widely separated in space and/or time) to collaborate [1]. Subversion (SVN) is a version control system initiated in 2000 by CollabNet Inc. It is used to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly-compatible successor to the widely used Concurrent Versions System (CVS) [2]. This little tutorial will help your team to set up a code repository for your term project and teach you the basics of SVN logic. What SVN allows, is to hold a central database of code and other files, so that they can be easily shared amongst members of the group. SVN logic functions as a tree, where the main folder is called the trunk and all subsequent subfolders are referred to as branches.
    [Show full text]
  • Introduction to Version Control
    1 Introduction to version control David Rey – DREAM 2 Overview • Collaborative work and version control • CVS vs. SVN • Main CVS/SVN user commands • Advanced use of CVS/SVN 3 Overview • Collaborative work and version control • CVS vs. SVN • Main CVS user commands • Advanced use of CVS 4 Collaborative work and version control: examples • Development • Source files: C, C++, java, Fortran, Tcl, Python, shell scripts, … • Build/config files: Makefile, ant, … • Text documents/articles/bibliographies • Plain text • Latex/bibtex • Web pages • Html • Php, javascripts, … • XML documents • ... 5 A software development process at INRIA • INRIA recommandations about software development: • http://www-sop.inria.fr/dream/rapports/devprocess/index.html • http://www-sop.inria.fr/dream/rapports/devprocess/main005.html#toc8 • « Best practices »: • CVS: http://www.tldp.org/REF/CVS-BestPractices/html/index.html • SVN: http://svn.collab.net/repos/svn/trunk/doc/user/svn-best-practices.html 6 Version control: main ideas • Distributed documents/collaborative work • Automatic merging • Alarms on conflicts • Easy communication between users (log messages, emails, …) • Version control: incremental versions • All previous versions available • Minimal necessary disk space (incremental) • History of changes/logs 7 Version control software • CVS: http://ximbiot.com/cvs/ • TortoiseCVS (http://www.tortoisecvs.org/) • WinCVS (http://www.wincvs.org/) • … • Subversion (SVN): http://subversion.tigris.org/ • TortoiseSVN (http://tortoisesvn.tigris.org/) • … • Forges that use
    [Show full text]
  • Getting Started W Ith CVS
    Getting Started W ith CVS An Oracle White Paper February 2005 Getting Started W ith CVS Introduction....................................................................................................... 3 W HAT IS CVS.................................................................................................. 3 terminology........................................................................................................ 3 CVS Step by step............................................................................................... 4 Downloading and Installing CVS............................................................... 4 Creating a Repository................................................................................... 5 Creating a CVS Connection........................................................................ 5 Configuring the Repository......................................................................... 6 Importing a Module...................................................................................... 7 Checking Out a Module............................................................................... 9 Adding Files................................................................................................... 9 Updating Files (Common)......................................................................... 10 Editing Files................................................................................................. 11 Deleting Files..............................................................................................
    [Show full text]
  • Tortoise Hg Guide
    TortoiseHg Documentation Release 3.1.0 Steve Borho and others October 08, 2014 CONTENTS 1 Preface 1 1.1 Audience ................................................. 1 1.2 Reading guide .............................................. 1 1.3 TortoiseHg is free! ............................................ 1 1.4 Community ................................................ 1 1.5 Acknowledgements ........................................... 2 1.6 Conventions used in this manual ..................................... 2 2 Introduction 3 2.1 What is TortoiseHg? ........................................... 3 2.2 Installing TortoiseHg ........................................... 3 3 What’s New 5 3.1 TortoiseHg 2.0 .............................................. 5 4 A Quick Start Guide to TortoiseHg 9 4.1 Configuring TortoiseHg ......................................... 10 4.2 Getting Acquainted ............................................ 11 4.3 Initialize the repository .......................................... 11 4.4 Add files ................................................. 12 4.5 Ignore files ................................................ 13 4.6 Commit .................................................. 13 4.7 Share the repository ........................................... 13 4.8 Fetching from the group repository ................................... 15 4.9 Working with your repository ...................................... 15 5 TortoiseHg in daily use 17 5.1 Common Features ............................................ 17 5.2 Windows Explorer Integration
    [Show full text]
  • Coding Horror: Setting up Subversion on Windows
    Coding Horror: Setting up Subversion on Windows http://www.codinghorror.com/blog/2008/04/setting-up-subversion... programming and human factors by Jeff Atwood * Apr 5, 2008 Seng up Subversion on Windows When it comes to readily available, free source control, I don't think you can do beer than Subversion at the moment. I'm not necessarily advocang Subversion; there are plenty of other great source control systems out there ‐‐ but few can match the ubiquity and relave simplicity of Subversion. Beyond that, source control is source control, as long as you're not using Visual SourceSafe . And did I menon that Subversion is ... free? Allow me to illustrate how straighorward it is to get a small Subversion server and client going on Windows . It'll take all of 30 minutes, tops, I promise. And that's assuming you read slowly. The first thing we'll do is download the latest Subversion Windows binary installer . At the me of wring, that's 1.46. I recommend overriding the default install path and going with something shorter: c:\svn\ Note that the installer adds c:\svn\bin to your path, so you can launch a command prompt and start working with it immediately. Let's create our first source repository, which is effecvely a system path. svnadmin create "c:\svn\repository" Within that newly created folder, uncomment the following lines in the conf/svnserve.conf file by removing the pound character from the start of each line: anon-access = none auth-access = write password-db = passwd Next, add some users to the conf/passwd file.
    [Show full text]
  • Winmerge Help
    WinMerge 2.14 Help Kimmo Varis Denis Bradford Dean Grimm Laurent Ganier Tim Gerundt Perry Rapp Christian List and all others who helped with this. Revision 1.5.13 Copyright © 2004-2013 Thingamahoochie Software. Information in this document is subject to change without notice. Other products and companies referred to herein are trademarks or registered trademarks of their respective companies or mark holders. About WinMerge Help This is Help for WinMerge 2.14. 1. Audience and scope WinMerge Help is intended for both new and experienced users. It explains how to use WinMerge, and documents its capabilities and limitations. 2. How to access Help WinMerge Help topics are provided in two forms: Microsoft HTML Help (WinMerge.chm), located in your WinMerge\Docs installation directory. HTML manual on the WinMerge Web site. You can access WinMerge Help in several ways: WinMerge Help menu While using WinMerge, click Help → WinMerge Help. HTML Help opens at the beginning (this topic). Context-sensitive help While using any WinMerge window, press F1. If a specific topic is available for your current window, Help opens at that topic. If not, Help opens at the beginning. WinMerge command line Use the /? or -? switch when running WinMerge from the command line. HTML Help opens at the beginning. WinMerge Web site Open your Web browser to winmerge.org. Under Documentation, follow the Manual link to the latest Help version. 3. How to use Help Please read the following topics to learn essential WinMerge basics, Quick start Gets you quickly started with WinMerge and shows its basic usage. Comparing and merging folders Explains the folder comparison window, available operations, and customizing the results display.
    [Show full text]
  • The Smart Home Engineering Dept. at Hwproducts, Inc
    Software Revision Control for MASS Git Installation / Configuration / Use Matthew Sell, CSSE Student MASS Research Participant, February 2014 Overview • Download / execute installer • Initial configuration • Clone repository Which Git? • Command-line (Windows, OS X, Linux) • http://git-scm.com • GUI (Windows) : TortoiseSVN-like • http://msysgit.github.io/ • http://code.google.com/p/tortoisegit/ • GUI (Windows, OS X) • http://www.sourcetreeapp.com • Eclipse Egit plugin • “Team” menu adequate for: add/commit/push/pull • Use “History” view for complex operations Installing Git “command-line”, Windows • Download installer from: http://git-scm.com • Run the installer, choose install folder • Default components are acceptable • Select “Run Git from the Windows Command Prompt” • “Use OpenSSH” • “Checkout Windows-Style, Commit Unix-Style” • Reboot not required Configuring Git “command-line”, Windows • Open a command prompt (run “cmd”) • git config –global user.name “Your Full Name” • git config –global user.email “your.email@address” • “Use Git Bash Only” option works fine • “Use OpenSSH” • “Checkout Windows-Style, Commit Unix-Style Installing TortoiseGit, Windows • Requires “command-line” Git – see slide #4 • Download installer from: http://code.google.com/p/tortoisegit/ • Run the installer • Select “OpenSSH, Git default SSH Client” • Default features are okay • Reboot not required Configuring TortoiseGit, Windows • Make sure “command-line” Git was configured (slide #5) Installing SourceTree, Windows • Download installer from: http://sourcetreeapp.com
    [Show full text]
  • Apexsql Source Control
    ApexSQL Source Control Version 2019.x Release Notes and Requirements System requirements Hardware Dual Core 2.0 GHz CPU 4 GB memory 153 MB disk space (depends on the number of linked databases) SQL Server SQL Server 2005 and higher [1] Azure SQL Database [1] Amazon RDS for SQL Server [1] Add-in integration SQL Server Management Studio 2012 and higher [2] OS Windows 7 SP1 / Windows Server 2008 R2 SP1 or higher [1] Software .NET Framework 4.7.2 or higher Note Source control integration available for Azure DevOps [4], Git [5], Mercurial [5], Subversion [5] and Perforce [5] Permissions and Windows user account with administrative privileges additional requirements See Minimum permissions required to install and use ApexSQL products See Permissions in ApexSQL Source Control See Remote access for SQL Server instance [1] See Supported systems for exact version support [2] You can use the latest full-featured backwards compatible SQL Server Management Studio for free. Click here [4] Azure DevOps Server (TFS) [5] / Azure DevOps Services [5] Up to the latest version Supported Software Windows version Windows 7 SP1 & Windows 8.1 & Windows 10 & Windows Server Windows Server Windows Server Windows Server Windows Server 2012 2019 2008 R2 SP1 2012 R2 2016 SQL Server version [3] 2017 2019 CTP 3 2005 2008 2012 2014 2016 Windows Linux [2] Windows Linux [2] ApexSQL Source Control SQL Server edition [3] Azure SQL Database Amazon RDS Express Standard Enterprise Single Managed for SQL Server Database, Instance Elastic Pool ApexSQL Source Control SQL Server
    [Show full text]
  • Introduction Slide
    HPCC Mid-Morning Break HPCC Version Control Systems Outline • What is version control? • Version Control Systems • VCS Hosting • Why use HPCC hosting? • Git Clients • Subversion Clients • Resources What is Version Control? • Tracks changes made to code by multiple contributors over time. • Can “rewind” to earlier versions without having to manually undo changes to code. • Can gracefully merge changes to the same file by different people in many cases. Version Control Systems 1 • Repositories Store files, information about the files, and changes to the files. Store history of changes to the files. • Tools Make working copies of repositories and update those copies. Copy changes from your working copy to repositories. Version Control Systems 2 • Good free and open source software is out there: Bazaar (bzr), Git, Mercurial (hg), and Subversion (svn). • HPCC officially supports Git and Subversion. • HPCC also provides CVS and Mercurial. VCS Hosting 1 • vcs.icer.msu.edu hosts Git and Subversion repositories which you can provide to arbitrarily-composed groups of collaborators. • CVS, Git, Mercurial, and Subversion are available on the HPCC dev nodes, but collaboration is more difficult there. VCS Hosting 2 • Git repositories can be accessed via HTTP, HTTPS, and SSH transports. • Subversion repositories can be accessed via SSH transport. (We will likely add HTTP and HTTPS transports later.) • CVS and Mercurial repositories are not presently hosted on vcs.icer.msu.edu. Why Use HPCC Hosting? • Private repositories can be shared among collaborators but excluded from public viewing. • No need to create a new account somewhere else (uses your MSU NetID). • Most hosting sites charge a fee for hosting private repositories (Assembla, Beanstalk, GitHub, etc...) or only accept public repositories (SourceForge, Savannah, etc...).
    [Show full text]