INTERNATIONAL GAMMA-RAY ASTROPHYSICS LABORATORY (INTEGRAL) Science Operations Centre Software Configuration Control Procedures (ISOC SCCP)

Size: px
Start display at page:

Download "INTERNATIONAL GAMMA-RAY ASTROPHYSICS LABORATORY (INTEGRAL) Science Operations Centre Software Configuration Control Procedures (ISOC SCCP)"

Transcription

1 INTERNATIONAL GAMMA-RAY ASTROPHYSICS LABORATORY () Science Operations Centre Software ( SCCP) INT-SOC-DOC-008 Issue 2.2 February 2004 Prepared by Maintained by Approved by M. Lever J. Treloar C. Brénéol L. Hansson

2 Page No : ii Distribution List ESTEC N. Dean L. Hansson F. Jacobs T. Lock J. Treloar Name Copies

3 Page No : iii Document Change Record Issue / Rev. Date Description 0 / 0 Jun 1999 First draft for internal review 1 / 0 Jul 1999 First Issue 2 / 0 Apr 2000 Section 7 added to the document 2 / 2 Feb 2004 Updated for operational use (SCREW 394)

4 Page No : iv Table Of Contents Distribution List...ii Document Change Record...iii Table Of Contents...iv List Of Figures...v 1. Introduction...vi 1.1 Reference Documents...vi 2. Directory Structure...vii 2.1 isoclib...vii 2.2 isoc...vii 3. Software Development...ix 3.1 CVS Tags and Branches...ix 4. Software Testing...x 4.1 Unit Level Testing...x 4.2 System Level Testing...x 5. Software Release...xii 6. External Deliveries...xiii 7....xv 7.1 Development practices...xv CVS procedures for use by the developers...xv Information about CVS...xix 7.2 Delivering code to the librarian...xx 7.3 Use of generic scripts for the applications...xxi Available scripts...xxi 7.4 Building an application...xxiii Procedure...xxiii Makefile...xxiii 7.5 Installation of the applications on the operational machines...xxiv Appendix A: Rose CM Commands...xxv Appendix B: Rose/Java Update Procedure...xxvi

5 Page No : v List Of Figures Figure 1: Figure 2: Figure 3: Figure 4: Figure 5: /isoclib directory...vii /isoc directory...viii /isoc/software/testing directory...x /isoc/software/master directory...xii /isoclib/deliveries directory...xiii

6 Page No : vi 1. Introduction This document is aimed at software developers to explain the system and procedures by which their software is kept under configuration control and what their responsibilities are to maintain this system. The directory structure used to store software source code developed by the and software delivered by third parties is described, as is the directory structure used to store run-time versions of the software. The way in which different versions of software packages are selected in the run-time area is explained. The procedures for meeting the software testing requirements are also described. 1.1 Reference Documents RD-1 RD-2 INT-SOC-PLN-002 Software Configuration Management Plan INT-SOC-PLN-003 Software Verification & Validation Plan

7 Page No : vii 2. Directory Structure There are two directories on the server which are used for configuration control of software, named /isoc and /isoclib. Both directories are owned by the isoclib account (the software librarian). 2.1 isoclib The isoclib directory is used to store the CVS repositories for software under development, and installations of externally delivered software. Figure 1: /isoclib directory The deliveries directory is where third party software is installed. Each new release of a software package is installed into a separate directory (see External Deliveries on page xiii). The _REPOS and _V5_REPOS directories are the CVS repositories for all software and documentation produced by the. The SGSWWW_REPOS directory is the CVS repository for all Internet related files: HTML scripts, CGI scripts, images etc. The STARMAP_REPOS directory is the CVS repository for all files related to starmap. 2.2 isoc This directory stores the run-time versions of software packages (or links to them) at various stages of development. This is where users should go to find (and run) the latest

8 Page No : viii release of a particular sub-system. Software which has been tested and released is stored in the master directory, software which is undergoing testing is stored in the testing directory, and untested software is stored in the development directory. This approach is consistent with [RD-1] which uses an integration directory instead of the testing directory ( testing is a more accurate name because integration will be performed in the development directory and the system level testing of that integration will be performed in the testing directory). The local directory stores software for use by individual, named, users. The development, testing, master and local directories are read-only for developers (only isoclib can write to these directories). Figure 2: /isoc directory The data directory contains any input files needed by software packages, e.g. PSFs required for mission planning. It also contains output files generated by software packages, e.g. POS and ICP files. The data_test directory has the same role, and is used for testing.

9 Page No : ix 3. Software Development A developer develops code in a working directory, usually in their home area. The working directory contains checked out copies of files from the repository. The directory /isoc/software/development contains directories for each sub-system. These sub-system directories contain untested versions of the software. Developers are free to build versions of their sub-systems in these directories (via the software librarian) to make them available, if required, to the users for feedback. It should be noted that because much of the Java source code, stored in the repository, is shared by all sub-systems, a build script or Makefile should be used to build the subsystem so that only the sources required for the sub-system are present; this keeps things clean and will simplify packaging the code for delivery when the time comes. 3.1 CVS Tags At various times during the development process, a developer may want to preserve particular versions of files so that they can be returned to later, for example, during testing, or after a build in the development directory. CVS allows files to be tagged with a symbolic name, either individually or (more commonly) as a group (e.g. a complete sub-system). The tag should be added by the developer, with a copy of the tag used sent to the software librarian, who will keep a record of all tags used. If software changes are to classes shared by two or more sub-systems, care should be taken that changes made for one sub-system do not break the behaviour of another subsystem which shares the classes. For example, once PGT is released, the versions of the classes it uses must be preserved, but development of those classes may need to continue for the other sub-systems.

10 Page No : x 4. Software Testing 4.1 Unit Level Testing Developers write test harnesses, where appropriate, to test a class (or a group of classes) which constitutes a unit. This is done in the developer s working directory. If a group of units are tested together, but all the units belong to the same component, the test is a higher level unit test. However, if the units are from different components, the test may be an integration test, depending on the purpose of the test, as determined by the developer. Either way, the test is performed in the developer s working directory. The developer is also responsible for documenting the tests (in accordance with [RD-2]). Once a developer has tested the unit and it meets the requirements of the unit level test, he should tag the files which make up the test (including the test harness files) so that the test can be reproduced at a later date. 4.2 System Level Testing The directories under /isoc/software/testing are used to store versions of sub-system software which are ready for system level testing. Figure 3: /isoc/software/testing directory

11 Page No : xi When a developer has a sub-system ready for system level testing, he should build it in the appropriate development directory. Then, as for unit level testing, he should tag the files and inform the software librarian who will perform a check out (using the tag) in the testing directory appropriate to the sub-system. The software will then be ready for testing by the assigned tester (who may not necessarily be the developer of the subsystem).

12 Page No : xii 5. Software Release Once a sub-system has successfully passed its system level tests, it is installed in an appropriate directory in /isoc/software/master, by the software librarian. Figure 4: /isoc/software/master directory The master directory is where software for delivery is taken from.

13 Page No : xiii 6. External Deliveries Deliveries of third party software packages are installed in isoclib/deliveries in a directory appropriate to the package. Figure 5: /isoclib/deliveries directory

14 Page No : xiv Subsequent deliveries of newer versions of software packages, or updates to them, are installed in new directories, with a soft-link used to point to the currently active version. The names of these directories indicate the software version number, as shown for the OMC software in Figure 5: /isoclib/deliveries directory. Keeping the software versions isolated in this way is important as it allows problems to be tracked easily and makes switching to a new package in the run-time area a simple matter of changing the link to point to the new version. If a problem is discovered with the latest release of a package, the link can be switched back to the old version while the problem is investigated.

15 Page No : xv 7. The procedures described below are MANDATORY practices for the development team. 7.1 Development practices The DD model is developed by the development team using Rose. The Rose DD model and the code are kept under configuration control under CVS. It is the developer responsibility to: - check-in modifications to the DD model and the code. - ensure that the checked-in Rose DD model and the code are consistent. - ensure that the modifications that have been done, do not break other developers code before checking-in the updated code/model. If conflicts arise, the developer shall talk with the other developers to solve the problem. The development team is very small (4 persons); this should allow the direct resolution of problems amongst the developers. Another possibility is to call an development team meeting in order to involve all the developers in the resolution of the problem CVS procedures for use by the developers CAUTION: When using CVS, always use the -n option first. This option allows you to see what the command will do without actually doing it. If the command works as expected, repeat the command without the -n option Creating your working environment If you create your working environment for the first time, you need to create a working directory (e.g. ) in your home area: mkdir ~/ cd ~/ You need to set the necessary environment variables. An ENV file where all the common paths are defined is maintained by the librarian. Add the following lines at the end of your.env file: setenv HOME $HOME/ source /isoclib/tools/env CAUTION: these lines needs to be added at the end of your.env to avoid re-definition of variables. The next time you login, or start a new shell, the ENV file will be sourced automatically when the.env file is sourced in.cshrc. For now though, just type: source.env

16 Page No : xvi Checking out files in your working environment To check files out of the repository, use: cvs co <path>/<file> where <path> is the directory tree to the file or directory you want relative to the $CVSROOT variable and <file> is the filename (not needed if you are checking out a directory). For example: cvs co docs/add will check out the latest version of the ADD into the directory you are currently in (make sure it s your working directory!), including the directory docs and any sub-directories inside ADD. Note that in this example, certain directories are needed to contain files generated by Rose or by scripts, and the variables which point to these directories may require the full directory hierarchy. Also note that you may need to check out the classdoc directory separately, if required, to avoid checking out the entire docs directory. Here s an example of how to check out an individual file: cvs co designs/isoc_add.mdl It also possible to use the modules defined by the librarian. When using the module name, all (and only) the necessary files are checked out. The librarian will inform the developers of the defined modules. For instance: cvs co ADD will automatically check out all the directories and files used to generate the ADD Comparing your working environment against the repository To compare your working environment with the repository, type: cvs -n update -A -P -d which will tell you the status of each file via a prefix letter: U = the file is in the repository but not in your working directory, or your working copy is out of date. A = the file has been added locally but is not yet part of the repository (see below for how to add files). R = the file has been removed locally but not yet removed from the repository (see below for how to remove files). M = the file has been modified in your working directory.? = the file is in your working directory but does not correspond to anything in the repository (see ADDING FILES below). C = a conflict occurred when CVS tried to merge the repository version of the file with

17 Page No : xvii your working version (does not apply to binary files) The -P option will remove from your working environment the directories deleted in the repository. The -A option will remove the sticky tags. The -d option will create the new directories which exist in the repository. The -n option prevents the update command from changing anything in your working directory, so if updates are required, you will need to repeat the command without the -n option. It is up to the developer to take proper action depending on the letter appearing in front of the file. In case a C letter appears, your should resolve the conflict. If you go ahead with updating (command without -n option) a file in front of which a C letter appears, your original working copy is renamed.#file.revision (where file is the filename, and revision is the checked out revision number) and the copy now in your working directory is the output of the rcsmerge command. You will need to resolve the conflicts in this file manually before the file can be checked in Committing your changes in repository Once your working files contain only your changes i.e. they are up to date, you can commit your local changes in the repository: cvs commit -m "Log message" <file> where <file> is the file to be checked in, or you can replace <file> with. to check in all modified files in the current directory (all with the same log message) Handling directories in the repository Adding or removing directories should only be done by the Librarian. If you need to add or remove a directory from the repository, contact the librarian. He will do it for you Adding files in the repository If you create a new file in your working directory, it can be checked in using: cvs add <file> cvs commit -m "Log message" <file> If you want to check in binary files (images, framemaker files, Rose files), use -kb option: cvs add -kb <file> cvs commit -m "Log message" <file> Removing files from the repository To remove a file from the repository, use the following on your working version of the file:

18 Page No : xviii rm <file> cvs remove <file> cvs commit -m "Log message" <file> With the last two commands, <file> may be omitted, in which case the commands will act on all the relevant files in the current directory (the files deleted using rm are still recorded in the local CVS directory). CAUTION: Removing files should be done very carefully and limited to the packages that you are responsible for. In case of doubt, contact the Librarian beforehand Viewing status of the working directory against the repository To view the status of the repository, you can use the CVS WWW pages accessible from the SGS WWW pages, via bullet CVS repositories under heading. Additionally, the following commands are useful to compare your working environment with the repository. > cvs diff -w <path>/<file> will list the differences between your working environment and the latest version of the files in the repository. > cvs diff -r tag1 <path>/<file> will list the differences between your working environment and a tagged version of a file in the repository. > cvs diff -r tag1 -r tag2 <path>/<file> will list the differences between two tagged versions of a file in the repository. > cvs status -v <path>/<file> will provide a status of a file (-v option includes the tags information of the file). > cvs log <path>/<file> will display all log information (versions, tags) of the specified file Tagging files When you are ready to make a delivery to the librarian, you can tag your delivery. Before tagging you need to clean and commit your changes (see ). The tagging will tag the version number of your local file. That is why it is very important to bring your working environment in line with the repository before tagging the files. You can use the script isoctag to tag your files (see ) or tag manually. Tagging Script The generic script is available in the repository to tag the java files, properties and data

19 Page No : xix file and start-up and build scripts used by a Java application (see ) Manual Tagging To tag the files manually, type: > cvs tag TAG_NAME Tag format The proposed tag format for identifying build versions of the software under CVS is as follows: A_BBB_CC_DD_EE where, A = D, I or M, indicating a development, integration or master (released) build (development versions are local to the developer) BBB = a three letter sub-system code e.g. PGT, PHS etc. CC = the major version number DD = the minor version number EE = a sub-minor version number (extra contingency, especially for minor test fixes) Information about CVS For those who are unfamiliar with CVS, there is a good introductory tutorial at More information can be found on the cvs man page (man cvs on the command line) or at:

20 Page No : xx 7.2 Delivering code to the librarian The steps to follow to deliver a sub-system to the librarian (for the users to test, etc...) are: view the status of your working environment (see ) clean your working environment as necessary commit your changes in (see ) tag the files of your delivery (see ). All the files used to build the applications and the building scripts shall be checkedin and tagged by the developers. verify that the tagged files are working go in a temporary directory (e.g. /local/isoc) check-out the tagged files (cvs co -r TAG_NAME) build the system using the building scripts try it Inform the librarian by . The shall specified the TAG_NAME set by the developer and the scripts to be used to build the system. The librarian will build the system from the tagged version of the files. If the building does not work, the librarian will not spend time to solve the problem and will bounce it back immediately to the developer.

21 Page No : xxi 7.3 Use of generic scripts for the applications Available scripts All the generic files written by the Librarian are located in the repository in $CVSROOT/tools/Scripts/build. They are used to build and install the java applications. Before using them, you should have your environment properly set (see ) isocmk isoctag This script creates a list of java source files for use with a Makefile and the isoctag script. The script automatically stores the list of java source files in a file named app.mk (e.g. phs.mk, oss.mk). The app.mk files are stored locally in $HOME/tools/Scripts/build. The script removes all *.class files below $CODE then builds the main java file assumed to be found at $CODE/isoc/taskmanagment/apptask/APP.java. The resulting *.class filenames are collected to form the list. To run the script: create app_extra.mk run the script: > isocmk app for example: isocmk pgt will automatically create the pgt.mk in $HOME/tools/Scripts/ build The isocmk list contains all the classes directly picked-up by the Java compiler. It excludes the test classes, the check classes, the colours classes (because of reflection), and the RMI classes. The isocmk script will automatically append the file app_extra.mk to the app.mk file. The file app_extra.mk is generated and maintained by the developer responsible for an application (see CIDL document). It contains the test classes, the check classes which are specific to each application. The developer responsible for building the application will generate and maintain the file app_extra.mk and store it in the Repository in $CVSROOT/tools/ Scripts/build. This script issues a cvs tag command for every file listed in app.mk. The file app.mk is the output from the isocmk command (see ). Additional files to be tagged as part of the delivery are listed in the app.tag file: these include data files (images, helps). The building files (Makefile, app.mk) will be tagged automatically. The developer responsible for an application (see CIDL document) will generate and maintain the file app.tag and store it in the repository in $CVSROOT/tools/ Scripts/build. To tag all the files of part of your application delivery:

22 Page No : xxii isocinstall commit all your changes (see ) run the script: > isoctag -n app Check the list of files displayed for error messages and missing files. Edit app.tag as necessary. If you need to edit app.mk you will need to check the entire build again (see ). Repeat the above command until the list of files is correct. run the script: > isoctag app Enter y to start tagging. For example: isoctag pgt will automatically tag all the files listed in pgt.mk and pgt.tag. This script builds an subsystem (e.g PLD, PGT, OSS) in the given install directory. Relies on a Makefile being present in $HOME/tools/Scripts/build with the given build target. It will create a jar file with all necessary classes and copy to the installation directory all additional files needed. To install the application app, type: > isocinstall app <tag> <install-dir> For example: isocinstall pgt D_PGT_01_21_09. will install PGT version in the current directory.

23 Page No : xxiii 7.4 Building an application Procedure create the list of java source files using isocmk (see ) list additional files part of the application in app.tag install the application using isocinstall (see ) build the application in the install directory: For debug use: > cd <install-dir> > make app > make JAVAC_FLAGS= -g app Makefile The Makefile is stored in th $CVSROOT//tools/Scripts/build and is maintained by the Librarian in conjunction with the developers. The Makefile defines the dependencies for each target app. For instance: pgt::$(java_objs) $(COLOUR_OBJS) $(RMI_CLASSES) The Makefile is designed to be used in conjunction with the isocmk script which produces a list of java source files stored in app.mk (see ). The list as in app.mk provides a definition for the JAVA_OBJS variable used in the Makefile. The RMI classes are listed under RMI_CLASSES variable, but these are not required for all subsystems. The RMI_CLASSES variable is defined in the Makefile itself. The COLOUR_OBJS variable is the same for all applications using it and is directly defined in the Makefile.

24 Page No : xxiv 7.5 Installation of the applications on the operational machines The applications will be installed by the System Administrator on the operational machines with the support of the developers and the Librarian. The application will be built on the development machine beforehand using the tagged files from the repository. The installed applications will be tar ed and copied onto a DAT for transfer to the operational machines. The necessary parameters will be set on the operational machines to make the application work (e.g. setting of environment variables). The developer responsible for an application will provide the installation instructions to the Librarian in a app_install.readme file.

25 Page No : xxv Appendix A: Rose CM Commands The Rose configuration management commands are accessed from the Units window (F7) and work as follows: Lock+Edit This will lock the unit (via CVS) for exclusive editing and give you a writable version. If someone else already has the unit locked, you will be warned, told who owns the lock and you will NOT get a writable version - go and talk to the owner of the lock. Undo Lock+Edit This reverses the Lock+Edit command above. If you have modified the unit, you will be warned and asked if you wish to revert changes ; typing y or yes means that your edits will be discarded. Note: if you discard your changes, you will need to reload the unit to remove the changes from the Rose model in memory; the file on disk will be as it was before your edits. Check In This performs a cvs commit on the unit. An editor will appear (determined by your $CVSEDITOR variable, or $EDITOR if $CVSEDITOR is not defined) for you to enter your log message. When you save and exit the editor, CVS will check the unit in. NOTE: DO NOT SET $CVSEDITOR to gvim! The gvim editor does not work with CVS and produces empty log messages. However, it can be used otherwise e.g. to edit source code. Update Rose Files This will update your working files by issuing a cvs update in your $HOME/ designs/ddd directory. Refresh Access Display This updates the access specifiers (n, r, w, m) shown to the left of the units in the packages list of the Units window (F7). You must have a unit selected before it will work. It is necessary to select this EVERY TIME another CM command is used 1. NOTE: All the script messages appear in xterm windows which remain visible for 60 seconds. You can remove them earlier than this by selecting the xterm window and pressing Control-C. 1. This is because Rose does not wait for a Rose exec command (which calls the shell script) to finish executing before proceeding to the next instruction in the menu script. This means that the menu script ends before the physical file permissions have changed, so Rose must be brought up to date manually when the shell script has ended and the physical file permissions have changed.

26 Page No : xxvi Appendix B: Rose/Java Update Procedure To keep the Java source code in line with the Rose model, all code should be generated from Rose, with the exception of method bodies which must be filled in separately. The following procedure should be adopted when updating source code: 1. Lock the Rose units which require changing. To prevent more than one person editing the same part of the model at the same time, the Lock+Edit command (see Appendix A: Rose CM Commands on page xxv) should be used in Rose. Units in the Logical View of the model are normally paired with a corresponding unit in the Component View; these have the suffixes cat and sub respectively. It is likely that both will need to be locked. 2. Edit the locked units in Rose. 3. Generate code for the locked units. Rose 98 has problems parsing anonymous classes, commonly used to define Listener objects inside method bodies. Unfortunately, if these classes already exist in a method body, they must be commented out before Rose will generate code. 4. Complete method bodies in the generated code as required. (Uncomment any anonymous classes, if appropriate.) 5. Compile the code. This means the code for the entire sub-system so that the next step will work. 6. Execute the code and check it works correctly. 7. Repeat steps 2 to 6 as necessary. 8. Commit the changed source code to the repository. 9. Commit the changed Rose units to the repository. Use the Check In command (see Appendix A: Rose CM Commands on page xxv).

Source Code Management/Version Control

Source Code Management/Version Control Date: 3 rd March 2005 Source Code Management/Version Control The Problem: In a typical software development environment, many developers will be engaged in work on one code base. If everyone was to be

More information

Workflow Administration of Windchill 10.2

Workflow Administration of Windchill 10.2 Workflow Administration of Windchill 10.2 Overview Course Code Course Length TRN-4339-T 2 Days In this course, you will learn about Windchill workflow features and how to design, configure, and test workflow

More information

Introduction to Windchill Projectlink 10.2

Introduction to Windchill Projectlink 10.2 Introduction to Windchill Projectlink 10.2 Overview Course Code Course Length TRN-4270 1 Day In this course, you will learn how to participate in and manage projects using Windchill ProjectLink 10.2. Emphasis

More information

Chapter 20: Workflow

Chapter 20: Workflow Chapter 20: Workflow 1 P a g e Table of Contents 1. About Workflow... 5 2. About this Guide... 5 3. Vital Information... 5 4. Security... 5 5. Activity... 5 6. Accessing Workflow... 6 7. Adding a Workflow...

More information

System Administration of Windchill 10.2

System Administration of Windchill 10.2 System Administration of Windchill 10.2 Overview Course Code Course Length TRN-4340-T 3 Days In this course, you will gain an understanding of how to perform routine Windchill system administration tasks,

More information

Using SVN to Manage Source RTL

Using SVN to Manage Source RTL Using SVN to Manage Source RTL CS250 Tutorial 1 (Version 092509a) September 25, 2009 Yunsup Lee In this tutorial you will gain experience using the Subversion (SVN) to manage your source RTL and code.

More information

Professional. SlickEdif. John Hurst IC..T...L. i 1 8 О 7» \ WILEY \ Wiley Publishing, Inc.

Professional. SlickEdif. John Hurst IC..T...L. i 1 8 О 7» \ WILEY \ Wiley Publishing, Inc. Professional SlickEdif John Hurst IC..T...L i 1 8 О 7» \ WILEY \! 2 0 0 7 " > Wiley Publishing, Inc. Acknowledgments Introduction xiii xxv Part I: Getting Started with SiickEdit Chapter 1: Introducing

More information

Working with a Version Control System

Working with a Version Control System Working with a Version Control System Summary Tutorial TU0114 (v2.4) March 18, 2008 This tutorial looks at how you can use Altium Designer s built-in version control capabilities to check project files

More information

using version control in system administration

using version control in system administration LUKE KANIES using version control in system administration Luke Kanies runs Reductive Labs (http://reductivelabs.com), a startup producing OSS software for centralized, automated server administration.

More information

Introduction to Windchill PDMLink 10.0 for Heavy Users

Introduction to Windchill PDMLink 10.0 for Heavy Users Introduction to Windchill PDMLink 10.0 for Heavy Users Overview Course Code Course Length TRN-3146-T 2 Days In this course, you will learn how to complete the day-to-day functions that enable you to create

More information

Introduction to Git. Markus Kötter koetter@rrzn.uni-hannover.de. Notes. Leinelab Workshop July 28, 2015

Introduction to Git. Markus Kötter koetter@rrzn.uni-hannover.de. Notes. Leinelab Workshop July 28, 2015 Introduction to Git Markus Kötter koetter@rrzn.uni-hannover.de Leinelab Workshop July 28, 2015 Motivation - Why use version control? Versions in file names: does this look familiar? $ ls file file.2 file.

More information

CS108, Stanford Handout #33. CVS in Eclipse

CS108, Stanford Handout #33. CVS in Eclipse CS108, Stanford Handout #33 Winter, 2006-07 Nick Parlante CVS in Eclipse Source Control Any modern software project of any size uses "source control" Store all past revisions - Can see old versions, see

More information

Windchill PDMLink 10.2. Curriculum Guide

Windchill PDMLink 10.2. Curriculum Guide Windchill PDMLink 10.2 Curriculum Guide Live Classroom Curriculum Guide Update to Windchill PDMLink 10.2 from Windchill PDMLink 9.0/9.1 for the End User Introduction to Windchill PDMLink 10.2 for Light

More information

Business Administration of Windchill PDMLink 10.0

Business Administration of Windchill PDMLink 10.0 Business Administration of Windchill PDMLink 10.0 Overview Course Code Course Length TRN-3160-T 3 Days After completing this course, you will be well prepared to set up and manage a basic Windchill PDMLink

More information

CVS versus BitKeeper A Comparison

CVS versus BitKeeper A Comparison Chapter 11 CVS versus BitKeeper A Comparison Since the publication of the second edition of this book, a powerful new versioning system has risen called Bitkeeper, or BK/PRO, to dominate at least certain

More information

Version control. HEAD is the name of the latest revision in the repository. It can be used in subversion rather than the latest revision number.

Version control. HEAD is the name of the latest revision in the repository. It can be used in subversion rather than the latest revision number. Version control Version control is a powerful tool for many kinds of work done over a period of time, including writing papers and theses as well as writing code. This session gives a introduction to a

More information

VERITAS NetBackup Microsoft Windows User s Guide

VERITAS NetBackup Microsoft Windows User s Guide VERITAS NetBackup Microsoft Windows User s Guide Release 3.2 Windows NT/95/98 May, 1999 P/N 100-001004 1994-1999 VERITAS Software Corporation. All rights reserved. Portions of this software are derived

More information

Eclipse Help

Eclipse Help Software configuration management We ll start with the nitty gritty and then get more abstract. Configuration and build Perdita Stevens School of Informatics University of Edinburgh 1. Version control

More information

15 Organisation/ICT/02/01/15 Back- up

15 Organisation/ICT/02/01/15 Back- up 15 Organisation/ICT/02/01/15 Back- up 15.1 Description Backup is a copy of a program or file that is stored separately from the original. These duplicated copies of data on different storage media or additional

More information

Local Version Control (sccs, rcs)

Local Version Control (sccs, rcs) Steven J Zeil February 21, 2013 Contents 1 History 2 2 Exploration 5 3 Collaboration 7 4 Strengths and Weaknesses 8 1 Localized Version Control The earliest version control systems in wide use were sccs

More information

Introduction to Subversion

Introduction to Subversion Introduction to Subversion Getting started with svn Matteo Vescovi 19/02/2010 Agenda A little bit of theory Overview of Subversion Subversion approach to Version Control Using Subversion Typical subversion

More information

DAVE Usage with SVN. Presentation and Tutorial v 2.0. May, 2014

DAVE Usage with SVN. Presentation and Tutorial v 2.0. May, 2014 DAVE Usage with SVN Presentation and Tutorial v 2.0 May, 2014 Required DAVE Version Required DAVE version: v 3.1.6 or higher (recommend to use the most latest version, as of Feb 28, 2014, v 3.1.10) Required

More information

Using SVN to Manage Source RTL

Using SVN to Manage Source RTL Using SVN to Manage Source RTL CS250 Tutorial 1 (Version 083010a) August 30, 2010 Yunsup Lee In this tutorial you will gain experience using the Subversion (SVN) to manage your source RTL and code. You

More information

Version Control Systems

Version Control Systems Version Control Systems ESA 2015/2016 Adam Belloum a.s.z.belloum@uva.nl Material Prepared by Eelco Schatborn Today IntroducGon to Version Control Systems Centralized Version Control Systems RCS CVS SVN

More information

Manual. CollabNet Subversion Connector to HP Quality Center. Version 1.2

Manual. CollabNet Subversion Connector to HP Quality Center. Version 1.2 Manual CollabNet Subversion Connector to HP Quality Center Version 1.2 A BOUT THE CONNECTOR About the Connector The CollabNet Subversion Connector to HP Quality Center enables Quality Center users to

More information

Table of Contents. The RCS MINI HOWTO

Table of Contents. The RCS MINI HOWTO Table of Contents The RCS MINI HOWTO...1 Robert Kiesling...1 1. Overview of RCS...1 2. System requirements...1 3. Compiling RCS from Source...1 4. Creating and maintaining archives...1 5. ci(1) and co(1)...1

More information

Essential Visual Studio Team System

Essential Visual Studio Team System Essential Visual Studio Team System Introduction This course helps software development teams successfully deliver complex software solutions with Microsoft Visual Studio Team System (VSTS). Discover how

More information

Version Control with Subversion

Version Control with Subversion Version Control with Subversion Introduction Wouldn t you like to have a time machine? Software developers already have one! it is called version control Version control (aka Revision Control System or

More information

BSM 9.0 ESSENTIALS. Instructor-Led Training

BSM 9.0 ESSENTIALS. Instructor-Led Training BSM 9.0 ESSENTIALS Instructor-Led Training INTENDED AUDIENCE New users of Business Service Management (BSM) 9.0, including: Database Administrators System Administrators Network Administrators Operations

More information

MATLAB & Git Versioning: The Very Basics

MATLAB & Git Versioning: The Very Basics 1 MATLAB & Git Versioning: The Very Basics basic guide for using git (command line) in the development of MATLAB code (windows) The information for this small guide was taken from the following websites:

More information

Using Subversion in Computer Science

Using Subversion in Computer Science School of Computer Science 1 Using Subversion in Computer Science Last modified July 28, 2006 Starting from semester two, the School is adopting the increasingly popular SVN system for management of student

More information

Software Delivery Integration and Source Code Management. for Suppliers

Software Delivery Integration and Source Code Management. for Suppliers Software Delivery Integration and Source Code Management for Suppliers Document Information Author Version 1.0 Version Date 8/6/2012 Status final Approved by Reference not applicable Subversion_for_suppliers.doc

More information

Version Control with Subversion and Xcode

Version Control with Subversion and Xcode Version Control with Subversion and Xcode Author: Mark Szymczyk Last Update: June 21, 2006 This article shows you how to place your source code files under version control using Subversion and Xcode. By

More information

Windchill Service Information Manager 10.2. Curriculum Guide

Windchill Service Information Manager 10.2. Curriculum Guide Windchill Service Information Manager 10.2 Curriculum Guide Live Classroom Curriculum Guide Introduction to Windchill Service Information Manager 10.2 Building Information Structures with Windchill Service

More information

Dalhousie University CSCI 2132 Software Development Winter 2015 Lab 7, March 11

Dalhousie University CSCI 2132 Software Development Winter 2015 Lab 7, March 11 Dalhousie University CSCI 2132 Software Development Winter 2015 Lab 7, March 11 In this lab, you will first learn how to use pointers to print memory addresses of variables. After that, you will learn

More information

VERITAS NetBackup TM 6.0

VERITAS NetBackup TM 6.0 VERITAS NetBackup TM 6.0 System Administrator s Guide, Volume II for UNIX and Linux N15258B September 2005 Disclaimer The information contained in this publication is subject to change without notice.

More information

HARFORD COMMUNITY COLLEGE 401 Thomas Run Road Bel Air, MD 21015 Course Outline CIS 110 - INTRODUCTION TO UNIX

HARFORD COMMUNITY COLLEGE 401 Thomas Run Road Bel Air, MD 21015 Course Outline CIS 110 - INTRODUCTION TO UNIX HARFORD COMMUNITY COLLEGE 401 Thomas Run Road Bel Air, MD 21015 Course Outline CIS 110 - INTRODUCTION TO UNIX Course Description: This is an introductory course designed for users of UNIX. It is taught

More information

Learn AX: A Beginner s Guide to Microsoft Dynamics AX. Managing Users and Role Based Security in Microsoft Dynamics AX 2012. Dynamics101 ACADEMY

Learn AX: A Beginner s Guide to Microsoft Dynamics AX. Managing Users and Role Based Security in Microsoft Dynamics AX 2012. Dynamics101 ACADEMY Learn AX: A Beginner s Guide to Microsoft Dynamics AX Managing Users and Role Based Security in Microsoft Dynamics AX 2012 About.com is a Rand Group Knowledge Center intended to provide our clients, and

More information

Novell ZENworks 10 Configuration Management SP3

Novell ZENworks 10 Configuration Management SP3 AUTHORIZED DOCUMENTATION Software Distribution Reference Novell ZENworks 10 Configuration Management SP3 10.3 November 17, 2011 www.novell.com Legal Notices Novell, Inc., makes no representations or warranties

More information

FileNet P8 Platform Directory Service Migration Guide

FileNet P8 Platform Directory Service Migration Guide FileNet P8 Platform Directory Service Migration Guide Release 3.5.1 November 2005 FileNet is a registered trademark of FileNet Corporation. All other product and brand names are trademarks or registered

More information

FileBench's Multi-Client feature

FileBench's Multi-Client feature FileBench's Multi-Client feature Filebench now includes facilities to synchronize workload execution on a set of clients, allowing higher offered loads to the server. While primarily intended for network

More information

Core Training Quick Reference Guide Version 2.0

Core Training Quick Reference Guide Version 2.0 Core Training Quick Reference Guide Version 2.0 Page 1 of 34 Contents Changes from Previous Version... 3 Introduction... 5 Guidance for Professional Users based in Colleges/ Schools/ Departments... 5 Logging

More information

Revision control systems (RCS) and

Revision control systems (RCS) and Revision control systems (RCS) and Subversion Problem area Software projects with multiple developers need to coordinate and synchronize the source code Approaches to version control Work on same computer

More information

Office 2010 Workflow;

Office 2010 Workflow; Office 2010 Workflow; Developing Collaborative Solutions MARK J. COLLINS Apress* Contents Preface About the Author About the Technical Reviewers Acknowledgements Introduction xix xxi xxii xxiii xxiv PART

More information

Job Scheduler Daemon Configuration Guide

Job Scheduler Daemon Configuration Guide Job Scheduler Daemon Configuration Guide A component of Mark Dickinsons Unix Job Scheduler This manual covers the server daemon component of Mark Dickinsons unix Job Scheduler. This manual is for version

More information

CISC 275: Introduction to Software Engineering. Lab 5: Introduction to Revision Control with. Charlie Greenbacker University of Delaware Fall 2011

CISC 275: Introduction to Software Engineering. Lab 5: Introduction to Revision Control with. Charlie Greenbacker University of Delaware Fall 2011 CISC 275: Introduction to Software Engineering Lab 5: Introduction to Revision Control with Charlie Greenbacker University of Delaware Fall 2011 Overview Revision Control Systems in general Subversion

More information

BlueJ Teamwork Tutorial

BlueJ Teamwork Tutorial BlueJ Teamwork Tutorial Version 2.0 for BlueJ Version 2.5.0 (and 2.2.x) Bruce Quig, Davin McCall School of Engineering & IT, Deakin University Contents 1 OVERVIEW... 3 2 SETTING UP A REPOSITORY... 3 3

More information

Basic System. Vyatta System. REFERENCE GUIDE Using the CLI Working with Configuration System Management User Management Logging VYATTA, INC.

Basic System. Vyatta System. REFERENCE GUIDE Using the CLI Working with Configuration System Management User Management Logging VYATTA, INC. VYATTA, INC. Vyatta System Basic System REFERENCE GUIDE Using the CLI Working with Configuration System Management User Management Logging Vyatta Suite 200 1301 Shoreway Road Belmont, CA 94002 vyatta.com

More information

MATLAB @ Work. MATLAB Source Control Using Git

MATLAB @ Work. MATLAB Source Control Using Git MATLAB @ Work MATLAB Source Control Using Git Richard Johnson Using source control is a key practice for professional programmers. If you have ever broken a program with a lot of editing changes, you can

More information

CSE 374 Programming Concepts & Tools. Laura Campbell (Thanks to Hal Perkins) Winter 2014 Lecture 16 Version control and svn

CSE 374 Programming Concepts & Tools. Laura Campbell (Thanks to Hal Perkins) Winter 2014 Lecture 16 Version control and svn CSE 374 Programming Concepts & Tools Laura Campbell (Thanks to Hal Perkins) Winter 2014 Lecture 16 Version control and svn Where we are Learning tools and concepts relevant to multi-file, multi-person,

More information

Microsoft Visual Studio Integration Guide

Microsoft Visual Studio Integration Guide Microsoft Visual Studio Integration Guide MKS provides a number of integrations for Integrated Development Environments (IDEs). IDE integrations allow you to access MKS Integrity s workflow and configuration

More information

University of Toronto

University of Toronto 1 University of Toronto APS 105 Computer Fundamentals A Tutorial about UNIX Basics Fall 2011 I. INTRODUCTION This document serves as your introduction to the computers we will be using in this course.

More information

Version Control Tools

Version Control Tools Version Control Tools Source Code Control Venkat N Gudivada Marshall University 13 July 2010 Venkat N Gudivada Version Control Tools 1/73 Outline 1 References and Resources 2 3 4 Venkat N Gudivada Version

More information

Managing Software and Configurations

Managing Software and Configurations 55 CHAPTER This chapter describes how to manage the ASASM software and configurations and includes the following sections: Saving the Running Configuration to a TFTP Server, page 55-1 Managing Files, page

More information

Graphviz Website Installation, Administration and Maintenance

Graphviz Website Installation, Administration and Maintenance Graphviz Website Installation, Administration and Maintenance 1 Overview The graphviz.org website is based on the Drupal content management system. Drupal uses a MySql database to store web pages and information

More information

Installing Globodox Web Client on Windows Server 2012

Installing Globodox Web Client on Windows Server 2012 Installing Globodox Web Client on Windows Server 2012 Make sure that the Globodox Desktop Client is installed. Make sure it is not running. Note: Please click on Allow or Continue for all required UAC

More information

INF 111 / CSE 121. Homework 4: Subversion Due Tuesday, July 14, 2009

INF 111 / CSE 121. Homework 4: Subversion Due Tuesday, July 14, 2009 Homework 4: Subversion Due Tuesday, July 14, 2009 Name : Student Number : Laboratory Time : Objectives Preamble Set up a Subversion repository on UNIX Use Eclipse as a Subversion client Subversion (SVN)

More information

1.3 How to backup system with Microsoft Windows System Backup

1.3 How to backup system with Microsoft Windows System Backup Windows System Backup Guide Backup/Restore Windows Systems Backup This chapter will describe in detail how to use Servosity Professional to backup your Microsoft Windows system and how you can restore

More information

TIBCO Administrator User s Guide. Software Release 5.7.1 March 2012

TIBCO Administrator User s Guide. Software Release 5.7.1 March 2012 TIBCO Administrator User s Guide Software Release 5.7.1 March 2012 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY

More information

Lab 2 : Basic File Server. Introduction

Lab 2 : Basic File Server. Introduction Lab 2 : Basic File Server Introduction In this lab, you will start your file system implementation by getting the following FUSE operations to work: CREATE/MKNOD, LOOKUP, and READDIR SETATTR, WRITE and

More information

TUTORIALS. version 17.0

TUTORIALS. version 17.0 TUTORIALS version 17.0 No Magic, Inc. 2011 All material contained herein is considered proprietary information owned by No Magic, Inc. and is not to be shared, copied, or reproduced by any means. All information

More information

Windows PowerShell. 3.0 Step by Step. Ed Wilson

Windows PowerShell. 3.0 Step by Step. Ed Wilson Windows PowerShell 3.0 Step by Step Ed Wilson Foreword Introduction xix xxi Chapter 1 Overview of Windows PowerShell 3.0 1 Understanding Windows PowerShell 1 Using cmdlets 3 Installing Windows PowerShell

More information

Scheduler Job Scheduling Console

Scheduler Job Scheduling Console Tivoli IBM Tivoli Workload Scheduler Job Scheduling Console Feature Level 1.3 (Revised December 2004) User s Guide SC32-1257-02 Tivoli IBM Tivoli Workload Scheduler Job Scheduling Console Feature Level

More information

SAS. 9.3 Guide to Software Updates. SAS Documentation

SAS. 9.3 Guide to Software Updates. SAS Documentation SAS 9.3 Guide to Software Updates SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2011. SAS 9.3 Guide to Software Updates. Cary, NC: SAS Institute

More information

IBM DB2 Data Archive Expert for z/os:

IBM DB2 Data Archive Expert for z/os: Front cover IBM DB2 Data Archive Expert for z/os: Put Your Data in Its Place Reduce disk occupancy by removing unused data Streamline operations and improve performance Filter and associate data with DB2

More information

Avaya Network Configuration Manager User Guide

Avaya Network Configuration Manager User Guide Avaya Network Configuration Manager User Guide May 2004 Avaya Network Configuration Manager User Guide Copyright Avaya Inc. 2004 ALL RIGHTS RESERVED The products, specifications, and other technical information

More information

Change Management for Rational DOORS User s Guide

Change Management for Rational DOORS User s Guide Change Management for Rational DOORS User s Guide Before using this information, read the general information under Appendix: Notices on page 58. This edition applies to Change Management for Rational

More information

TIBCO ActiveMatrix BusinessWorks Plug-in for Big Data User s Guide

TIBCO ActiveMatrix BusinessWorks Plug-in for Big Data User s Guide TIBCO ActiveMatrix BusinessWorks Plug-in for Big Data User s Guide Software Release 1.0 November 2013 Two-Second Advantage Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE.

More information

QlikView 11 Source Control Walkthrough

QlikView 11 Source Control Walkthrough QlikView 11 Source Control Walkthrough A QlikView Technology White Paper Originally published: August, 2011 Updated August, 2012 www.qlikview.com 1 Table of Contents BACKGROUND... 3 SOURCE CONTROL BASICS...

More information

2010 MegaPath Inc. All rights reserved. Confidential and Proprietary 2

2010 MegaPath Inc. All rights reserved. Confidential and Proprietary 2 Polycom SIP Phones Base Configuration for MegaPath Duet Hosted Voice Service Contents Summary... 3 Configuration Settings Overview... 3 Restarting the Phone... 5 Rebooting the Phone... 6 Uploading Log

More information

Using Git for Project Management with µvision

Using Git for Project Management with µvision MDK Version 5 Tutorial AN279, Spring 2015, V 1.0 Abstract Teamwork is the basis of many modern microcontroller development projects. Often teams are distributed all over the world and over various time

More information

Introduction to Source Control ---

Introduction to Source Control --- Introduction to Source Control --- Overview Whether your software project is large or small, it is highly recommended that you use source control as early as possible in the lifecycle of your project.

More information

Before you can use the Duke Ambient environment to start working on your projects or

Before you can use the Duke Ambient environment to start working on your projects or Using Ambient by Duke Curious 2004 preparing the environment Before you can use the Duke Ambient environment to start working on your projects or labs, you need to make sure that all configuration settings

More information

ACTIVE DIRECTORY DEPLOYMENT

ACTIVE DIRECTORY DEPLOYMENT ACTIVE DIRECTORY DEPLOYMENT CASAS Technical Support 800.255.1036 2009 Comprehensive Adult Student Assessment Systems. All rights reserved. Version 031809 CONTENTS 1. INTRODUCTION... 1 1.1 LAN PREREQUISITES...

More information

Lab Exercise Part II: Git: A distributed version control system

Lab Exercise Part II: Git: A distributed version control system Lunds tekniska högskola Datavetenskap, Nov 25, 2013 EDA260 Programvaruutveckling i grupp projekt Labb 2 (part II: Git): Labbhandledning Checked on Git versions: 1.8.1.2 Lab Exercise Part II: Git: A distributed

More information

Windows PowerShell Cookbook

Windows PowerShell Cookbook Windows PowerShell Cookbook Lee Holmes O'REILLY' Beijing Cambridge Farnham Koln Paris Sebastopol Taipei Tokyo Table of Contents Foreword Preface xvii xxi Part I. Tour A Guided Tour of Windows PowerShell

More information

Dealer Tutorial. Uplink Customer Service 1-888-9UPLINK sales@uplink.com. 2010 Uplink Security, LLC. All rights reserved.

Dealer Tutorial. Uplink Customer Service 1-888-9UPLINK sales@uplink.com. 2010 Uplink Security, LLC. All rights reserved. Welcome to the u-traq Dealer Tutorial Uplink Customer Service 1-888-9UPLINK sales@uplink.com 2010 Uplink Security, LLC. All rights reserved. Table of Contents I. Device Overview Introduction to u-traq

More information

WORKING IN TEAMS WITH CASECOMPLETE AND MICROSOFT VISUAL SOURCE SAFE. Contents

WORKING IN TEAMS WITH CASECOMPLETE AND MICROSOFT VISUAL SOURCE SAFE. Contents WORKING IN TEAMS WITH CASECOMPLETE AND MICROSOFT VISUAL SOURCE SAFE Contents Working in Teams with CaseComplete... 2 Need an introduction to how version control works?... 2 Exclusive Checkout... 3 Multiple

More information

SVN Starter s Guide Compiled by Pearl Guterman June 2005

SVN Starter s Guide Compiled by Pearl Guterman June 2005 SVN Starter s Guide Compiled by Pearl Guterman June 2005 SV Table of Contents 1) What is SVN?... 1 2) SVN Architecture... 2 3) Creating a Working Copy... 3 4) Basic Work Cycle... 4 5) Status Symbols...

More information

OpenGeo Suite for Linux Release 3.0

OpenGeo Suite for Linux Release 3.0 OpenGeo Suite for Linux Release 3.0 OpenGeo October 02, 2012 Contents 1 Installing OpenGeo Suite on Ubuntu i 1.1 Installing OpenGeo Suite Enterprise Edition............................... ii 1.2 Upgrading.................................................

More information

Our Kids Information Technology Department IT Backup and Restore Procedure

Our Kids Information Technology Department IT Backup and Restore Procedure 1 of 7 Our Kids Information Technology Department IT Backup and Restore Procedure I. Policy/Purpose: This Policy describes Our Kids of Miami-Dade/Monroe, Inc. (Our Kids) Information Technology (IT) Department

More information

Implementing and Administering an Enterprise SharePoint Environment

Implementing and Administering an Enterprise SharePoint Environment Implementing and Administering an Enterprise SharePoint Environment There are numerous planning and management issues that your team needs to address when deploying SharePoint. This process can be simplified

More information

Version control tracks multiple versions. Configuration Management. Version Control. V22.0474-001 Software Engineering Lecture 12, Spring 2008

Version control tracks multiple versions. Configuration Management. Version Control. V22.0474-001 Software Engineering Lecture 12, Spring 2008 Configuration Management Version Control V22.0474-001 Software Engineering Lecture 12, Spring 2008 Clark Barrett, New York University Configuration Management refers to a set of procedures for managing

More information

Version Control with Svn, Git and git-svn. Kate Hedstrom ARSC, UAF

Version Control with Svn, Git and git-svn. Kate Hedstrom ARSC, UAF 1 Version Control with Svn, Git and git-svn Kate Hedstrom ARSC, UAF 2 Version Control Software System for managing source files For groups of people working on the same code When you need to get back last

More information

Librarian. Integrating Secure Workflow and Revision Control into Your Production Environment WHITE PAPER

Librarian. Integrating Secure Workflow and Revision Control into Your Production Environment WHITE PAPER Librarian Integrating Secure Workflow and Revision Control into Your Production Environment WHITE PAPER Contents Overview 3 File Storage and Management 4 The Library 4 Folders, Files and File History 4

More information

Arbortext Content Manager 10.1. Curriculum Guide

Arbortext Content Manager 10.1. Curriculum Guide Arbortext Content Manager 10.1 Curriculum Guide Live Classroom Curriculum Guide Introduction to Arbortext Content Manager 10.1 Business Administration of Arbortext Content Manager 10.1 Workflow Administration

More information

HAHTsite IDE and IP Installation Guide

HAHTsite IDE and IP Installation Guide HAHTsite IDE and IP Installation Guide IDE and IP Installation Guide release 4.0 Notice Copyright 1999 HAHT Software, Inc. All Rights Reserved May 1999 MN01-C-00-400-00 No part of this publication may

More information

Introducing Xcode Source Control

Introducing Xcode Source Control APPENDIX A Introducing Xcode Source Control What You ll Learn in This Appendix: u The source control features offered in Xcode u The language of source control systems u How to connect to remote Subversion

More information

Using RSMACC version control system with AB Industrial programming Controllers and files.

Using RSMACC version control system with AB Industrial programming Controllers and files. Using RSMACC version control system with AB Industrial programming Controllers and files. RSMACC (Rockwell Software Maintenance Automation Control Center) 2003. Credits: Peter Tiagunov LeanMES, Free Academic

More information

Fred Hantelmann LINUX. Start-up Guide. A self-contained introduction. With 57 Figures. Springer

Fred Hantelmann LINUX. Start-up Guide. A self-contained introduction. With 57 Figures. Springer Fred Hantelmann LINUX Start-up Guide A self-contained introduction With 57 Figures Springer Contents Contents Introduction 1 1.1 Linux Versus Unix 2 1.2 Kernel Architecture 3 1.3 Guide 5 1.4 Typographical

More information

Git - Working with Remote Repositories

Git - Working with Remote Repositories Git - Working with Remote Repositories Handout New Concepts Working with remote Git repositories including setting up remote repositories, cloning remote repositories, and keeping local repositories in-sync

More information

REQUEST FOR PROPOSAL SUPPLY, INSTALLATION AND CUSTOMIZATION OF HELPDESK SOFTWARE. Tender No. ECIL / CSD / 10-3053 dated 27.05.2011

REQUEST FOR PROPOSAL SUPPLY, INSTALLATION AND CUSTOMIZATION OF HELPDESK SOFTWARE. Tender No. ECIL / CSD / 10-3053 dated 27.05.2011 REQUEST FOR PROPOSAL FOR SUPPLY, INSTALLATION AND CUSTOMIZATION OF HELPDESK SOFTWARE Tender No. ECIL / CSD / 10-3053 dated 27.05.2011 ELECTRONICS CORPORATION OF INDIA LTD ( A Government of India Enterprise

More information

Jazz Source Control Best Practices

Jazz Source Control Best Practices Jazz Source Control Best Practices Shashikant Padur RTC SCM Developer Jazz Source Control Mantra The fine print Fast, easy, and a few concepts to support many flexible workflows Give all users access to

More information

Setting up Radmind For an OSX Public Lab

Setting up Radmind For an OSX Public Lab Setting up Radmind For an OSX Public Lab Radmind consists of a set of about ten Unix Commands installed on both the client and server machines. A GUI application, called Radmind Assistant, provides a simplified

More information

Version Control! Scenarios, Working with Git!

Version Control! Scenarios, Working with Git! Version Control! Scenarios, Working with Git!! Scenario 1! You finished the assignment at home! VC 2 Scenario 1b! You finished the assignment at home! You get to York to submit and realize you did not

More information

Modulo II Software Configuration Management - SCM

Modulo II Software Configuration Management - SCM Modulo II Software Configuration Management - SCM Professor Ismael H F Santos ismael@tecgraf.puc-rio.br April 05 Prof. Ismael H. F. Santos - ismael@tecgraf.puc-rio.br 1 Bibliografia Introduction to Apache

More information

Installation Guide: Delta Module Manager Launcher

Installation Guide: Delta Module Manager Launcher Installation Guide: Delta Module Manager Launcher Overview... 2 Delta Module Manager Launcher... 2 Pre-Installation Considerations... 3 Hardware Requirements... 3 Software Requirements... 3 Virtualisation...

More information

Rational Application Developer Performance Tips Introduction

Rational Application Developer Performance Tips Introduction Rational Application Developer Performance Tips Introduction This article contains a series of hints and tips that you can use to improve the performance of the Rational Application Developer. This article

More information

Version Control. Luka Milovanov lmilovan@abo.fi

Version Control. Luka Milovanov lmilovan@abo.fi Version Control Luka Milovanov lmilovan@abo.fi Configuration Management Configuration management is the management of system change to software products Version management: consistent scheme of version

More information

Sophos Anti-Virus for Linux configuration guide. Product version: 9

Sophos Anti-Virus for Linux configuration guide. Product version: 9 Sophos Anti-Virus for Linux configuration guide Product version: 9 Document date: September 2015 Contents 1 About this guide...5 2 About Sophos Anti-Virus for Linux...6 2.1 What Sophos Anti-Virus does...6

More information