Frequently used SVN Commands

SVN COMMANDS

SVN Commit – Commit/Chekins changes into Repo

Syntax:
$ svn commit -m "Enter Log messages"

SVN Diff – To See Difference in files

Syntax:
$ svn diff filename

SVN Status – Status of the working copy

Syntax:
$ svn status PATH

SVN add — Add files, directories, or symbolic links

Syntax:
$ svn add path

SVN copy (cp) — Copy a file or directory in a working copy or in the repository.

Syntax:
$ svn copy foo.txt bar.txt

SVN mkdir — Create a new directory under version control.

Syntax:
$ svn mkdir URL

Examining History in Subversion

Your Subversion repository is like a time machine. It keeps a record of every change ever committed and allows you to explore this history by examining previous versions of files and directories as well as the metadata that accompanies them.

Several commands can provide you with historical data from the repository:



svn log

Shows you broad information: log messages with date and author information attached to revisions and which paths changed in each revision

svn diff

Shows line-level details of a particular change

svn cat

Retrieves a file as it existed in a particular revision number and displays it on your screen

svn list

Displays the files in a directory for any given revision



Subversion's Components


Subversion, once installed, has a number of different pieces. The following is a quick overview of what you get. 



svn

The command-line client program

svnversion

A program for reporting the state (in terms of revisions of the items present) of a working copy

svnlook

A tool for directly inspecting a Subversion repository

svnadmin

A tool for creating, tweaking, or repairing a Subversion repository

mod_dav_svn

A plug-in module for the Apache HTTP Server, used to make your repository available to others over a network

svnserve

A custom standalone server program, runnable as a daemon process or invokable by SSH; another way to make your repository available to others over a network.

svndumpfilter

A program for filtering Subversion repository dump streams

svnsync

A program for incrementally mirroring one repository to another over a network

The Roles & Responsibilities of a 'Build and Release Engineer'

The Build and Release Engineer will play a main role in the SDLC life cycle

Roles & Responsibilities :-

• Work with Engineering, Operations, Quality Assurance and Project Management to define and execute projects that implement build, release and deployment of web software.

• Manage the source code control system.

• Develop an automated, continuous, build process that reviews the source code, identifies build errors and notifies appropriate parties to expedite/facilitate synchronization to the latest build.

• Improve productivity by designing & developing full-featured build systems; implementing tools and scripts that enable efficient, flexible builds (Shell, Perl,Python,groovy)

•  Develop an efficient deployment process for web deployments.

• Identify and propagate best practices and processes

• Communicate releases related activities to all the stakeholders and take their feedback to improve the process.
•Implement Continuous integration in organisation


Skillset Required :-

• Extensive experience working with Cruise Control,Jenkins,Hudson and other build tools

• Operational knowledge in Java, Apache, Tomcat, database

• Source control tools: Experience in at least one source control tool like GIT, CVS, Perforce, Subversion  etc. Experience in administrating one of these tools is a plus.

• Build scripting: Fluency in any of the build scripting languages like ANT, nANT, make, Maven,Gradle

• General scripting: Good knowledge of a scripting language like Perl, Python, Unix/Windows scripting is preferred

• Bug tracking Tools: Working experience of one defect tracking system (Bugzilla, Jira,Mantis etc.)

• General understanding of the platform in which you work (J2EE,.Net)..