The document is a seminar report on Subversion (SVN), an open-source version control system that aids in file sharing for concurrent development. It discusses the components of SVN, including servers, client software, and repository structure, as well as essential operations like checkout, commit, and update. Additionally, it outlines best practices for using SVN and provides references for further information.

1. INDIRA GANDHI GOVT ENGG. COLLEGE SAGAR
SUBMITTED TO --
MR. R.S.S. RAWAT
(HOD OF IT)
SUBMITTED BY--
PRANJAL SONI
0601IT131031
GUIDEDED BY --
MISS KHUSHBU JAIN

2. SEMINAR REPORT ON

3. CONTENTS
 WHAT IS SVN ??
 WHAT IS VERSION CONTROL ??
 SVN SERVERS
 SVN CLIENT SOFTWARE
 REPOSITORY
 OPERATIONS
 RULES

4. WHAT IS SVN
SVN IS THE FREE OPEN SOURCE VERSION CONTROL SYSTEM
MANAGES FILE SHARING FOR CONCURRENT DEVELOPMENT
THIS ALLOWS DEVELOPERS TO WORK CONCURRENTLY WITH
THE CENTRAL CODE BASE

5. WHAT IS VERSION CONTROL
ALLOW SHARING FILES OVER THE NETWORK
SUPPORT AUTHORITY AND SECURITY
ALLOW CHECKING OF MODIFICATION

6. SVN SERVERS
ASSEMBLA
VISUAL SVN
UBER SVN
WANDISCO

7. VISUAL SVN
 IT IS THE STAND ALONE APPLICATION
 IT MAKES LOCAL MACHINE AS THE SERVER
 TYPICAL SUVERSION SETUP FOR TAEM WORK INVOLVES A
SINGLE SERVER MACHINE BEING ACCESSED FROM
CLIENTSON COMPUTERS

8. VISUAL SVN IS BASED ON CVS

9. ASSEMBLA
 IT IS THE WEB BASED REPOSITORY
 ASSEMBLA PROVIDES WORLDS BEST HOSTING OF
SUBVERSION IN CLOUD
 IT IS SECURE, RELIABLE AND INTEGRATED

10. SVN CLIENT SOFTWARES
TORTOISE
SVN
ECLIPSE
SVN
PLUGIN
SMART -
SVN

11. WORK CYCLE
svn checkout
svn update
CREATE A LOCAL COPY
svn add
svn move
svn delete
MAKE CHANGES
svn status -u
SEE WHAT IS CHANGED
IN THE REPOSITORY IN MEANTIME
svn update
UPDATE THE LOCAL COPY
svn diff
svn resolved
RESOLVE CONFLICTS
(MERGE CHANGES)
svn commit
SUBMIT YOUR CHANGES
105
100
106
Subversion
Repository

12. REPOSITORY
 IT IS THE HEART OF ANY VERSION CONTROL
 EVERY REPOSITORY IS IDENTIFIED BY IT’S URL
 REPOSITORY WORKING AS A
SERVER AND VERSIONING
TOOL WORKING AS CLIENT

13. tags
branches
trunk
Project 1
Root
Project 2
SUBVERSION REPOSITORY LAYOUT
tags
branches
trunk
tags
trunk
Project 1
Repository parent dir
Project 2
tags
trunk
ONE REPOSITORY MANY
PROJECT
ONE PROJECT PER REPOSITORY
branches
branches

14. REPOSITORY
BRANCH
TAG
TRUNK

15.  HERE THE INTIAL AND WORKING COPY OF PROJECT IS
PLACED
 IT IS ALWAYS STAY STABLE (WITHOUT ANY COMPILATION
ERROR)
TRUNK

16. TAG
 THIS DIRECTORY IS USED TO STORE NAMED SNAPSHOTS OF
THE PROJECT
 GIVE THE MEMORABLE NAME TO
SPECIFIC VERSION IN THE
REPOSITORY

17. BRANCHES
 TO DEVELOP ANY ADDITIONAL FUNCTIONALITY TO THE
PROJCET
 ALSO DOING WORK
PARALLALY

18. OPERATIONS
CHECKO
UT
COMMIT
UPDATE
ADD
DELETE
REVERT
DIFF
LOCK
SHOW LOGS

19. SVN CHECKOUT
 FOR GETTING CODE FROM SVN SERVER TO OUR LOCAL
MACHINE FOR FIRST TIME

20. SVN-COMMIT
 TO SAVE CHANGES FROM
LOCAL MACHINE TO THE SERVER
SVN-UPDATE
 TO GET THE CHANGES DONE BY OTHERS

21. SVN ADD ( )

22. SVN-DELETE

23. SVN DIFF
 IF WE WANT TO SEE THE DIFFERENCE BETWEEN OUR LOCAL
CHANGES AND REPOSITORY CODE
SVN LOCK
 IF VERY FREQUENT COMMIT ARE HAPPENING ON A FILE
 GET A LOCK WOULD NOT ALLOW ANYBODY ELSE TO
COMMIT ANY CHANGES TO THAT FILE UNLESS THE LOCK IS
RELEASED

24.  NORMAL STATUS
 FILE HAS BEEN MODIFIED AND NOT COMITTED
 CONFLICT OCCUR DURING UPDATE
 NEW FILE IS ADDED INTO THE LOCAL MACHINE BUT NOT
ON THE SERVER
 FILE IS LOCKED

25. SVN REVERT
 REVERTS ANY LOCAL CHANGES TO A FILE OR DIRECTORY
AND RESOLVES ANY CONFLICTED STATES

26. REVISION NUMBERS
0 1 2 3
Revision number is increased for every
transaction that changes the repository.

27. RULES
 BEFORE COMMITING PERFORM AN UPDATE ON THE WHOLE
SOURCE CODE
 WHEN ADDING NEW FILES TO THE EXISTING SOURCE CODE
ALWAYS PERFORM SVN ADD THEN SVN COMMIT

28. REFRENCES
 WWW.EBOOK-DL.COM
 WWW.WIKIPEDIA.COM
 WWW.VISUALSVN.COM
 WWW.TORTOISESVN.COM

29. THANK YOU!!!!